commit-gnuradio
[Top][All Lists]
Advanced

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

[Commit-gnuradio] git://gnuradio.org/jabele branch, prefix, updated. a33


From: git repository hosting
Subject: [Commit-gnuradio] git://gnuradio.org/jabele branch, prefix, updated. a33cbffaf802c5c3018596fcf592e37c978acfb6
Date: Wed, 10 Feb 2010 18:04:02 +0000 (GMT)

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/jabele".

The branch, prefix has been updated
  discards  412119344774b56cc6dfd3df1199a15164defaa5 (commit)
       via  a33cbffaf802c5c3018596fcf592e37c978acfb6 (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 (412119344774b56cc6dfd3df1199a15164defaa5)
            \
             N -- N -- N (a33cbffaf802c5c3018596fcf592e37c978acfb6)

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 a33cbffaf802c5c3018596fcf592e37c978acfb6
Author: Jason Abele <address@hidden>
Date:   Thu Feb 4 17:38:33 2010 -0800

    Fixed creation of burn-usrp2-eeprom, burn-usrp4-eeprom
    
    Added $prefix from configure to paths

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

Summary of changes:


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




reply via email to

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