1 From: author@payflex.com
3 Subject: [cbas] topic branch updated. $new_commit_hash
4 X-Git-Refname: refs/heads/topic
6 X-Git-Oldrev: $old_commit_hash
7 X-Git-Newrev: $new_commit_hash
9 The branch, topic has been updated
10 discards $old_commit_abbrev create branch on topic 2
11 via $new_commit_abbrev rewind and continue branch on topic
13 This update added new revisions after undoing existing revisions. That is
14 to say, the old revision is not a strict subset of the new revision. This
15 situation occurs when you --force push a change and generate a repository
16 containing something like this:
18 * -- * -- B -- O -- O -- O ($old_commit_hash)
20 N -- N -- N ($new_commit_hash)
22 When this happens we assume that you've already had alert emails for all
23 of the O revisions, and so we here report only the revisions in the N
24 branch from the common base, B.
26 Those revisions listed above that are new to this repository have
27 not appeared on any other notification email; so we list those
28 revisions in full, below.
30 - Log -----------------------------------------------------------------
32 commit $new_commit_hash
33 Author: A U Thor <author@example.com>
34 Date: $new_commit_date
36 rewind and continue branch on topic
40 index 55da47f..a30ab5b 100644
45 +rewind and continue branch
47 -----------------------------------------------------------------------
51 1 files changed, 1 insertions(+), 1 deletions(-)