commit-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Commit-gnuradio] git://gnuradio.org/jblum branch, next, updated. e100a0


From: git version control
Subject: [Commit-gnuradio] git://gnuradio.org/jblum branch, next, updated. e100a06a41e683afb59531e09ad4dca7b7888a57
Date: Thu, 22 Mar 2012 02:11:53 +0000 (UTC)

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 "git://gnuradio.org/jblum".

The branch, next has been updated
  discards  e11aac1a6a236d6f509778ff96521b4fc23b5e5e (commit)
       via  e100a06a41e683afb59531e09ad4dca7b7888a57 (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 (e11aac1a6a236d6f509778ff96521b4fc23b5e5e)
            \
             N -- N -- N (e100a06a41e683afb59531e09ad4dca7b7888a57)

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 e100a06a41e683afb59531e09ad4dca7b7888a57
Author: Josh Blum <address@hidden>
Date:   Wed Mar 21 19:14:22 2012 -0700

    updated submodule

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

Summary of changes:
 grextras |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
git://gnuradio.org/jblum



reply via email to

[Prev in Thread] Current Thread [Next in Thread]