This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "UNNAMED PROJECT". The branch, jerlbeck/master has been updated discards 01f5df9589e83f97f9b15e31b06a53cfe4192e6d (commit) discards d6108ac1e13b9701b4bc2c5b2dba360ac231b589 (commit) discards 5a7dd909fe51a9925ca844cdfcba48e0a890fb56 (commit) discards cfdd37fa164f8918fe6dea33b0212d01133f98e5 (commit) discards e3859a113af4d7865831a7f778574f830de8b23f (commit) via 57cf69a18ccceac4b250dceb56c4e0d5f0018a95 (commit) via dd08ac86e6fa1ea69e78c344424d72fc9d79d6d7 (commit) via bae33a70019e2344053eae3798856364cdb8aa12 (commit) via 5e46a20e030a71816a20935befadf232968e1ff6 (commit) via c135b878cd7a155431b4f000e9c00be07e157222 (commit) via 1139ec1d0f20014bb17ea5d5cb65478b4489a8e7 (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (01f5df9589e83f97f9b15e31b06a53cfe4192e6d) \ N -- N -- N (57cf69a18ccceac4b250dceb56c4e0d5f0018a95) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: src/sba.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT