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 "Repository for Bering-uClibc.".
The branch, apkg-using-gpg has been updated
discards 26af841199033cad0bf9b81c5d02b014f569f4f7 (commit)
via c1ba2a5662c1402e78564838a3c7218eac8dcaf8 (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 (26af841199033cad0bf9b81c5d02b014f569f4f7)
\
N -- N -- N (c1ba2a5662c1402e78564838a3c7218eac8dcaf8)
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 c1ba2a5662c1402e78564838a3c7218eac8dcaf8
Author: Erich Titl <[email protected]>
Date: Sat Sep 1 00:40:38 2018 +0200
Added ntp.drift stub to keep buildtool happy
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
Repository for Bering-uClibc.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
leaf-git-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-git-commits
