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? -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <james...@debian.org>
signature.asc
Description: Digital signature
