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, unpacked-next has been updated
discards 4649ac768cbf42865d30c4b8ed4585038e92ba54 (commit)
via 07ae8fd3cc0f031e938cc4c7802f7d9fede1d362 (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 (4649ac768cbf42865d30c4b8ed4585038e92ba54)
\
N -- N -- N (07ae8fd3cc0f031e938cc4c7802f7d9fede1d362)
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 07ae8fd3cc0f031e938cc4c7802f7d9fede1d362
Author: Erich Titl <[email protected]>
Date: Fri Aug 30 16:18:58 2019 +0200
Adapted buildtool control files to unpacked mode
Updated e2fsprogs to upstream 1.4.3
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
Repository for Bering-uClibc.
_______________________________________________
leaf-git-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-git-commits
