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, clean-master has been updated
discards 9ccdaf3020edc4814bf612cc717a9689f2a5e6cf (commit)
discards cfbd6046abb47a0fce08f5b74c9c1d8ec0ca2381 (commit)
via 333830da4c1230ba3014441b5890ec6fa4d46454 (commit)
via f23d9f62674dcbcc9e0884f1b0eca9a3f0f3c64f (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 (9ccdaf3020edc4814bf612cc717a9689f2a5e6cf)
\
N -- N -- N (333830da4c1230ba3014441b5890ec6fa4d46454)
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 333830da4c1230ba3014441b5890ec6fa4d46454
Author: Erich Titl <[email protected]>
Date: Sat Jul 2 16:32:17 2022 +0200
Do a checkout master in the checkout target of buildtool.mk to
assert the state of the repository before checking out
a specific tag.
commit f23d9f62674dcbcc9e0884f1b0eca9a3f0f3c64f
Author: Erich Titl <[email protected]>
Date: Sat Jul 2 16:22:32 2022 +0200
Removed scan and restart buttons from show_progress.
They are not necessary here.
-----------------------------------------------------------------------
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
