tag 650744 moreinfo thanks Hi,
I'm not sure I understand. Normally, the workflow is that you commit individual things, without touching debian/changelog, that have a 'Closes: #nnnn' in the commit message, on which the hook will act upon. Once you then release, you will create the changelog with git-dch from the previous commit message, so debian/changelog will have the 'Closes: #nnnn' again, which will make the bugs closed in the bts after a successful upload to the archive. Now, you're suggesting that the bts hook should act twice upon the 'Closes: #nnnn', once to mark them pending when you commit it (based on the commit message), and once when you do a release commit containing debian/changelog additions (based on the content of the commit)? In the first workflow, which I consider to be the only sane one, this would trigger the bts hook twice. I don't think that is a good idea. Regards, Daniel -- Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: [email protected] Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
