[pkg-db-commits] [db-defaults] branch master updated (83c65df -> a5bf4f9)

Ondrej Sury ondrej at alioth.debian.org
Sun Oct 27 14:08:06 UTC 2013


This is an automated email from the git hooks/post-receive script.

ondrej pushed a change to branch master
in repository db-defaults.

  discards  83c65df   prepare 1:5.3.21~exp1 release
  discards  e460325   Update gbp.conf
  discards  dd795ef   Revert "Update from 5.3 to 6.0"
  discards  7c63c35   prepare 6.0.19+1~exp1 release
  discards  af58b25   Remove M-A: foreign from libdb-java, since it was wrong
  discards  1a0eaf9   prepare 6.0.19+1~exp1 release
  discards  be40549   Update from 5.3 to 6.0
  discards  7f62855   prepare 5.3.1~exp2 release
  discards  7f2bce0   Add Multi-Arch support (Closes: #647869)
  discards  c3fd936   prepare 5.3.1~exp1 release
  discards  2fd211b   Add db-upgrade-util package
  discards  e188d90   prepare 5.3~exp1 release
  discards  4a23c5b   prepare 5.3 release
  discards  c077527   Update dependencies to db5.3
      adds  6a59e96   Add db-upgrade-util package
      adds  10f8464   Add Multi-Arch support (Closes: #647869)
      adds  9c90fe3   Bump standards version to 3.9.3
      adds  beec6a0   prepare 5.1.5 release
      adds  c50fe82   Remove M-A: foreign from libdb-java, since it was wrong
      adds  26fa108   prepare 5.1.6 release
      adds  c72da6d   Update db-upgrade-util for jessies
      adds  7a7f480   prepare 5.1.7 release
      adds  9af8296   Update gbp.conf for debian-jessie
       new  eb7dbe9   Update dependencies to db5.3
       new  c7f973b   prepare 5.3 release
       new  9a16a84   prepare 5.3~exp1 release
       new  0253b9a   prepare 5.3.1~exp1 release
       new  ab84a88   Add Multi-Arch support (Closes: #647869)
       new  55892e8   prepare 5.3.1~exp2 release
       new  a5bf4f9   Remove M-A: foreign from libdb-java, since it was wrong

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (83c65df)
            \
             N -- N -- N   refs/heads/master (a5bf4f9)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omits" are not gone; other references still
refer to them.  Any revisions marked "discards" are gone forever.

The 7 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:
 debian/changelog |   34 +++++++++++++++++++++-------------
 debian/control   |    4 ++--
 debian/gbp.conf  |    4 +---
 3 files changed, 24 insertions(+), 18 deletions(-)

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-db/db-defaults.git



More information about the pkg-db-commits mailing list