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, fix-install has been updated
discards 2045e774ff874453e598cc8cf4d21d08bd4ceb33 (commit)
via c41c492dc4b3995a9ba0694c930000f61cbbe751 (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 (2045e774ff874453e598cc8cf4d21d08bd4ceb33)
\
N -- N -- N (c41c492dc4b3995a9ba0694c930000f61cbbe751)
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 c41c492dc4b3995a9ba0694c930000f61cbbe751
Author: Erich Titl <[email protected]>
Date: Sun Aug 25 16:09:30 2019 +0200
Added lost initrd.lrp and initrd.lrp.sig to KERNEL_AND_MODULES
-----------------------------------------------------------------------
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
