On Fri, Jun 24, 2011 at 02:51:41PM +0200, Joachim Breitner wrote: > Hi, > > Am Freitag, den 24.06.2011, 07:40 -0400 schrieb James Vega: > > On Fri, Jun 24, 2011 at 10:54:43AM +0200, Joachim Breitner wrote: > > > debcommit -r is great as it integrates well into other uses of > > > debcommit. But when the source is maintained using a VCS helper such as > > > git-buildpackage or git-dpm, it is unfortunate that it creates different > > > tags than these. Also, those may add more tags, e.g. for the > > > corresponding patched state. > > > > > > Hence, if debcommit could find out whether the source is managed by > > > git-buildpackage (e.g. if debian/.gbp.conf is present) or by git-dpm (in > > > which case debian/.git-dpm will be present) and then use the appropriate > > > tool to tag the release, that would be very nice. > > > > I don't use either of those tools. What would be the appropriate way to > > tag when those tools are in use? > > git-buildpackage --git-tag-only (possibly with --git-sign-tags) > and > git-dpm tag
Note that in the gbp case --git-tag-only will also run the post-tag hooks. If it helps git-buildpackage could also get a --print-tag option which would print the tag it would create. Cheers, -- Guido > > Greetings, > Joachim > > -- > Joachim "nomeata" Breitner > Debian Developer > nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C > JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
