E.g., I'm tracking:
http://git.savannah.gnu.org/cgit/quagga.git/log/?h=volatile/patch-tracking/1/proposed/ff
Where:
* 1/ is an arbitrary tracking cycle Id that I'll bump (so history is
preserved and I don't have to rewrite it and people can look at old
history). It could be an ISO-format date too.
* proposed/ is an umbrella namespace for what I've caught from the list
and other people's repos
* proposed/ff under that is a branch of contributions that don't conflict
and could be 'fast-forward' merged. Any patches that conflict would go
in separate heads under proposed/
Could have a separate '<cycle id>/reject/ for rejected commits, to make it
explicit, or just leave it to be deduced from what isn't in master when a
new cycle-id appears?
Not completely sure about the namespace or whether it should be published
in the main git repo. If we went with a gitolite somewhere, I'd probably
make it its own repo to keep the main repo namespace clean.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
Testing can show the presense of bugs, but not their absence.
-- Dijkstra
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
