Your message dated Thu, 10 Aug 2017 19:04:43 +0000
with message-id <e1dfsl9-0008cr...@fasolo.debian.org>
and subject line Bug#867214: fixed in git-buildpackage 0.9.0~exp3
has caused the Debian Bug report #867214,
regarding git-buildpackage: Strange format of commit message added by 
import-orig
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 ow...@bugs.debian.org
immediately.)


-- 
867214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-buildpackage
Version: 0.8.17
Severity: normal

Hi,

gbp import-orig stared producing merge commit messages like 
this one:


    Updated version 20170702 from 'upstream/20170702'
    
    with Debian dir 43f841d7950f0587745d57c8c87fd79e1aed60dd


which I don't really like for the three following reasons:

1. The commit message uses a really bizzare format of:
   
    A description of the change split for some

    reason in the middle of a sentence

instead of:
   
    Short summary of the change

    More detailed description possibly consisting of several
    lines or even paragraphs with each sentence ended with 
    a trailing dot.

2. I am not native speaker, and maybe that's why I have an impression
that a small word "to" is missing in "Updated version 20170702". But to
be honest I can't really see the need of duplicating the version number
in the same line. Prevously the version was mentioned once in the summary, 
and once in the long description, what IMHO looked much better:

    Merge tag 'upstream/20161007'
    
    Upstream version 20161007

3. The commit message uses past tense ("Updated"), where previously infinitive
was used (e.g. "Merge").



It would be nice if all those three items could be fixed. In my opinion
something like this:

    Merge tag 'upstream/20170702'

    Update to upstream version 20170702
    with Debian dir 43f841d7950f0587745d57c8c87fd79e1aed60dd.

would but better, but as I wrote I am not a native.

Regards,
robert
  

--- End Message ---
--- Begin Message ---
Source: git-buildpackage
Source-Version: 0.9.0~exp3

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.

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 867...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guido Günther <a...@sigxcpu.org> (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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 10 Aug 2017 14:57:39 -0300
Source: git-buildpackage
Binary: git-buildpackage git-buildpackage-rpm
Architecture: source
Version: 0.9.0~exp3
Distribution: experimental
Urgency: medium
Maintainer: Guido Günther <a...@sigxcpu.org>
Changed-By: Guido Günther <a...@sigxcpu.org>
Description:
 git-buildpackage - Suite to help with Debian packages in Git repositories
 git-buildpackage-rpm - Suite to help with RPM packages in Git repositories
Closes: 596513 682854 867214
Changes:
 git-buildpackage (0.9.0~exp3) experimental; urgency=medium
 .
   [ Guido Günther ]
   * [ce76320] doc: properly mark filter as repeatable in the gbp-import-dsc
     synopsis
   * [01a4a7f] dch: support passing arbitrary dch command line options
     (Closes: #596513, #682854)
   * [f208a0b] import_orig: use a more gittish commit message.
     When replacing the debian/ dir don't used past tense and
     keep the subject more like git-merge. (Closes: #867214)
   * [3e4e795] buildpackage: don't prepare any tarballs in overlay mode.
     They're not in git so we fail otherwise
   * [66138d9] buildpackage: pass the proper tarball dir for overlays.
     We want to look for tarballs in tarball dir (if specified) not the output
     dir
   * [da42f70] buildpackge: add test for overlay mode
   * [b71a89e] export: print names of generated tarballs when using
     pristine-tar so we get as much information as with git-archive.
   * [3ff0fc7] pristine-tar: properly separate additional tarballs by spaces
 .
   [ Maximiliano Curia ]
   * [a20047b] export_source: replace orig_file with
     source.upstream_tarball_name orig_file was dropped in
     8edd16022d75967a8fe54ef99a0733400a287bc2
Checksums-Sha1:
 ba953d9b6273f94ae559a55d35060b4033915e7b 2308 git-buildpackage_0.9.0~exp3.dsc
 9bc46816877e1d3c383918c11d91f095034bd4e7 2324664 
git-buildpackage_0.9.0~exp3.tar.xz
 22609798aae53645a3724920c325d76d656b9dab 12442 
git-buildpackage_0.9.0~exp3_amd64.buildinfo
Checksums-Sha256:
 b288ac1c26f3e411b8030ec0637c420bb47da0198f9a0eb20797efca1489018b 2308 
git-buildpackage_0.9.0~exp3.dsc
 6db8b12b9127ed60b335d2285f1847809d2b11d768b8a6bb1bed105954725cf6 2324664 
git-buildpackage_0.9.0~exp3.tar.xz
 8bc5b7835a755f48504ef4c99aa39f432ead2e92788c073700bce8b9646338ad 12442 
git-buildpackage_0.9.0~exp3_amd64.buildinfo
Files:
 f698ddb529bcfef49a0552e87d3f198e 2308 vcs optional 
git-buildpackage_0.9.0~exp3.dsc
 ddd4aee6ad5ef0ddd1a13fbbb11a984b 2324664 vcs optional 
git-buildpackage_0.9.0~exp3.tar.xz
 fb7fba91d94d36fd6c5efe9dfdcf6222 12442 vcs optional 
git-buildpackage_0.9.0~exp3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEvHzQcjh1660F3xzZB7i3sOqYEgsFAlmMqsIACgkQB7i3sOqY
Egsoxw//QutlkkfmdPeScoH/V0v7/pxI2O3OvH10plL21fMDmIKUjM+sG4Pm7eAB
8e0i8Z6eB9ON1LN0Kp1LlQR+jKUWytW/gLEWSTCjQbY0hu+o1oEG9BAJI4ifWZju
mlTwXm35ZO+PaCvR1gX6DyT3KyOinZeoKYjWtuFAzs5gYqE/TAzRirrJLR0tTSBZ
ZSMOdDQOyeTN9GmAibBAGHC+T43OOYj0lbTBOxAsAahnLYuVnMlW4+4mYLDMMaiV
SxMSFlExE/TJpKMgtK5EQyJH9euaJ5wjaRCQerIV0/FPKfcFXFslmcuScrY5KTo/
h8WfhhbVrbf2d+bYgqfgRZ+F4UzvOd0Q67AdCeZGx54XALwobMavC1yWqxE/Ctz+
7A7Y5yKw3UtKNA+DkeMZIzF5DWvHAq/S+PSv/pYUiDaMuoTia7A0AZkrhldNjzud
g8dfqUutbRBZkBRTZXc0EeJE8RjHCsP3nSGilpsHx+Y3eOKHxW5yFwYw+uRTNF7b
wzI9NDrFE/zm25PXX+yc343037GSaPjm7ypMTWJasD4V96Inf2QW/aHC/n3qmY5n
68FjYcu554uNs5SDJVa9ebOr9OM2fYMF7tvrS7874YWj/bmGEcwpUh6WQlV/021b
0hsgnAP+Hze8cKKVpQYy+15cR6gieMK95LnQF6Pw5Eo+IsUkCfI=
=aaeV
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to