On Tue, 22 Sep 2015, Martin Winter wrote:
If the major work you try to solve is tracking changes to submitted
patches, then this might work.
It's a bit of a pain. Mailing lists aren't great for tracking patches -
providing canonical IDs for issues and associated patches as they are
updated particularly. Patchwork helps a bit, but even so, it would require
contributors to be super-diligent about setting --in-reply-to when using
git send-email, and when replying on list, and that's far from the case -
and also requires digging (e.g. list archives don't always make it easy to
get the message-id).
5) Curious on other choices and their pros/cons…
Another option would be to require that patches are submitted via
bugzilla. There's a fairly good git/bugzilla tool to let you push and pull
patches between them, and even add/edit comments from the commandline -
'git bz' - which at least some GNOME folk use.
Discussion can still happen on list, just refer to the bugzilla ID. Ditto,
link to the thread in the list-archive in a bugzilla comment.
That would at least make it easier to give a stable ID to a patch set, and
allow the patches to be easily updated while retaining the stable ID.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
If you teach your children to like computers and to know how to gamble
then they'll always be interested in something and won't come to no real harm.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
