There is also a git bugzilla module, developed by a GNOME dev, which is
reasonable. The only issue I've had is that there's some problem in
determining the proxy to use via libproxy in the python module it uses.
See: http://blog.fishsoup.net/2008/11/16/git-bz-bugzilla-subcommand-for-git/
Note, there is also a different bugzilla plugin for git. I have not
tried it.
Say someone files a bug, BUGID. You make a fix. Now you can do:
git bz attach BUGID HEAD
This attaches the commit to the bug report and updates the commit with
the bugzilla URI. You can change 'HEAD' to a list of commits, or a
range, and that should work.
You can tweak the fix and commit with --amend, and do:
git bz attach -e HEAD
and it will automatically know the bugid to update.
When it works, and the bug is confirmed fixed:
git bz push
to close the bugzilla issue, etc.
You can create new bugzilla bugs from within git with 'git bz file',
which attaches commits like 'attach' does. You can apply patches
attached to bugzilla bugs to your local repo with 'git bz apply'. There
is also an 'edit' command that lets you add comments to bugs or change
status, by bugid /or/ by the git commit id.
The +ve of this is that it is easy to try out. We already have a
bugzilla, and this seems to provide nice integration between the git
repo command line and the bugzilla and wider users.
The biggest change would be agreeing that submissions be done via
bugzilla.
Also note that this doesn't /require/ the use of this specific git
plugin.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
love, n.:
When it's growing, you don't mind watering it with a few tears.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
