Your message dated Mon, 17 Mar 2008 13:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#468118: fixed in git-buildpackage 0.4.21
has caused the Debian Bug report #468118,
regarding git-buildpackage: Include full commit message in changelog
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
468118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468118
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.4.16
Severity: wishlist

It would be nice for git-dch to have an option to include the full
commit message in the changelog.  It would of course have to re-wrap
and indent paragraphs a bit.  That way, I could say Closes: #nnnnnn in
the commit message for future reference and also have it appear in the
changelog -- sort of debcommit in reverse.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (99, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages git-buildpackage depends on:
ii  devscripts                   2.10.13     Scripts to make the life of a Debi
ii  git-core                     1:1.5.4.2-2 fast, scalable, distributed revisi
ii  python                       2.4.4-6     An interactive high-level object-o
ii  python-support               0.7.6       automated rebuilding support for p

git-buildpackage recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: git-buildpackage
Source-Version: 0.4.21

We believe that the bug you reported is fixed in the latest version of
git-buildpackage, which is due to be installed in the Debian FTP archive:

git-buildpackage_0.4.21.dsc
  to pool/main/g/git-buildpackage/git-buildpackage_0.4.21.dsc
git-buildpackage_0.4.21.tar.gz
  to pool/main/g/git-buildpackage/git-buildpackage_0.4.21.tar.gz
git-buildpackage_0.4.21_all.deb
  to pool/main/g/git-buildpackage/git-buildpackage_0.4.21_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Guenther <[EMAIL PROTECTED]> (supplier of updated git-buildpackage 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 14 Mar 2008 20:42:53 +0100
Source: git-buildpackage
Binary: git-buildpackage
Architecture: source all
Version: 0.4.21
Distribution: unstable
Urgency: low
Maintainer: Guido Guenther <[EMAIL PROTECTED]>
Changed-By: Guido Guenther <[EMAIL PROTECTED]>
Description: 
 git-buildpackage - Suite to help with Debian packages in Git repositories
Closes: 468118
Changes: 
 git-buildpackage (0.4.21) unstable; urgency=low
 .
   * allow meta tags in the commit logs
   * add --full and --meta options --full (Closes: #468118)
Files: 
 ae161a007f9d2c0bf19e866162c79d08 714 devel optional git-buildpackage_0.4.21.dsc
 b861de8586577533abe84ce7bbaef56e 36814 devel optional 
git-buildpackage_0.4.21.tar.gz
 e024ecdd3725c6b3ce1720555c061412 50348 devel optional 
git-buildpackage_0.4.21_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH3nT/n88szT8+ZCYRAk7CAJ4y8UceSdvo/93HeNG/NijfVWXgogCfbCAq
Od3nHVH2+2fzs6LL3repKU0=
=BuN1
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to