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, apkg-using-gpg has been updated
  discards  8a90ddb94111a2bde58cd48b2309941d528ed7f3 (commit)
       via  717ec4dd3ce67079e54333df7167bb2819ffac3a (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 (8a90ddb94111a2bde58cd48b2309941d528ed7f3)
            \
             N -- N -- N (717ec4dd3ce67079e54333df7167bb2819ffac3a)

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 717ec4dd3ce67079e54333df7167bb2819ffac3a
Author: Erich Titl <[email protected]>
Date:   Sun Aug 12 12:57:46 2018 +0200

    made strip package a function in apkg
    added option -if to apkg to make handling of configdb quiet
    first attempt to enable apkg -u with signed packages

-----------------------------------------------------------------------

Summary of changes:


hooks/post-receive
-- 
Repository for Bering-uClibc.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
leaf-git-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-git-commits

Reply via email to