On Fri, 1 Jul 2016, Martin Winter wrote:
http://ipv6.gossamer-threads.com/lists/quagga/dev/30142?search_string=FreeBSD%20Testing%20Update;#30142
Unless you claim that this only applied to the proposed/6 branch. I
took this as an agreement for general work on proposed branches.
Ah, that was for r6, at that time.
It's not really possible to not rebase stuff at all, while still in the
process of reviewing and sorting pending stuff.
The commit ID will be stable.
But this doesn’t solve the issue on tracking where things broke. I
would need to tag the test runs with every commit ID included in the
code. Not really a solution…
So basically, you want to be able to pick up a series of CI runs across
the set of proposes patches from where you left off - assuming some fix
is proposed for a previous issue?
What we could do is tag how far the CI got (i.e. the commit before the
one where it breaks), then add in the fix as appropriate (which might
require rebasing and changing the series from the commit where it
broke), and then you continue?
regards,
--
Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
If God had a beard, he'd be a UNIX programmer.
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
