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 aadb17680d5ef1f5cb6d9a868a4f2977be15e0b8 (commit)
via 6732000912bbbcf210f14f0d1a641c4899bb1328 (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 (aadb17680d5ef1f5cb6d9a868a4f2977be15e0b8)
\
N -- N -- N (6732000912bbbcf210f14f0d1a641c4899bb1328)
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 6732000912bbbcf210f14f0d1a641c4899bb1328
Author: Erich Titl <erich.t...@think.ch>
Date: Tue Feb 15 14:52:37 2022 +0100
Small improvements in buildtool.mk avoiding multiple invocations
of patching the source code.
Also setting the git branch for the submodule busybox to the
desired value without touching buildtool.cfg as there is no tarball
anymore.
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
Repository for Bering-uClibc.
_______________________________________________
leaf-git-commits mailing list
leaf-git-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-git-commits
