It's unlikely, but warn the user to update first before telling them they need to...
[git-central.git] / tests / t2202-5.txt
1 From: author@payflex.com
2 To: commits@list.com
3 Subject: [cbas] topic branch updated. $new_commit_hash
4 X-Git-Refname: refs/heads/topic
5 X-Git-Reftype: branch
6 X-Git-Oldrev: $old_commit_hash
7 X-Git-Newrev: $new_commit_hash
8
9 The branch, topic has been updated
10   discards $old_commit_abbrev update branch with existing commits does not replay them on topic
11
12 This update discarded existing revisions and left the branch pointing at
13 a previous point in the repository history.
14
15  * -- * -- N ($new_commit_hash)
16             \
17              O -- O -- O ($old_commit_hash)
18
19 The removed revisions are not necessarilly gone - if another reference
20 still refers to them they will stay in the repository.
21
22 No new revisions were added by this update.
23
24 Summary of changes:
25  a |    2 +-
26  1 files changed, 1 insertions(+), 1 deletions(-)