On Sun, 07 Aug 2011 08:31:43 +0200, Dominique Dumont wrote: > How about a compromise between the 2 approaches and recommend the following: > 1/ update upstream tarball > 2/ update changelog with new version, and release=UNRELEASED > 3/ commit > 4/ work other debian files _while doing one commit per change_ > 5/ update changelog for the above changes in other debian files > 6/ dch -r > 7/ commit updated changelog That's what I've tried yesterday, so I'm fine with the workflow :) For 2/ I have [git-import-orig] postimport = dch -v%(version)s New upstream release. in my ~/.gbp.conf. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - PGP/GPG key ID: 0x8649AA06 : :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe `- NP: Dire Straits: Planet Of New Orleans
Attachment:
signature.asc
Description: Digital signature