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 "The official mkinitcpio repository".
The branch, master has been updated
discards bc41c8b3c51263e52ff21f5ff52fce5c778a35d9 (commit)
via b43739e39d9287baaec131f176a350736bffda4d (commit)
via 60713cf838baeaa59b71788aaa0fb421b0ecbcd5 (commit)
via 7984722e127d411d2c978eaa9665709b4a681485 (commit)
via 001a0559cd52d2ab600e31d192198062021e8898 (commit)
via 66ab66ebccfc66a8d3afd6f331b4548f6cd973a7 (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 (bc41c8b3c51263e52ff21f5ff52fce5c778a35d9)
\
N -- N -- N (b43739e39d9287baaec131f176a350736bffda4d)
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 -----------------------------------------------------------------
commit b43739e39d9287baaec131f176a350736bffda4d
Merge: 06bc15f 60713cf
Author: Giancarlo Razzolini