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, cleanup-init has been updated
discards e83418432a82198657c9dfd96be77176cefdcd82 (commit)
via 6b14e464a3d6dcb5fda28dff1a659cf9028f0c0f (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 (e83418432a82198657c9dfd96be77176cefdcd82)
\
N -- N -- N (6b14e464a3d6dcb5fda28dff1a659cf9028f0c0f)
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 6b14e464a3d6dcb5fda28dff1a659cf9028f0c0f
Author: Erich Titl <[email protected]>
Date: Sun Sep 30 17:52:17 2018 +0200
The setting of the system date to the year 2040 creates problems
with the date command. This commit sets the date in gpg_strip
to the first of january 2030 in case of gpg key date problems.
-----------------------------------------------------------------------
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
