Just as a heads up:
I should have full RFC compliance results for proposed 5 as of git
commit 5ab56c73c
(Nov 17 - when the BSD and Solaris issue still existed) in approx
another 6 hrs.
Current version is started as well and results should be available in
approx 36 hrs
(Doesn’t mean that you need to wait - this is just a heads up for your
planning)
- Martin
On 23 Nov 2015, at 9:06, Donald Sharp wrote:
Paul -
I don't mind pushing them up, but I wanted to solve the issue that
Martin
has discovered about the FSM log message first if you don't mind?
donald
On Mon, Nov 23, 2015 at 5:09 AM, Paul Jakma <[email protected]> wrote:
On Mon, 16 Nov 2015, Donald Sharp wrote:
Currently everything queued up is at:
https://github.com/donaldsharp/quagga/tree/volatile/patch-tracking/5/proposed/ff
Can you push them to Savannah?
Savannah doesn't allow non-ff updates of branches, so after a rebase
of a
published volatile branch you need to delete it and recreate (*never*
do
this for master). This is what I do:
for H in deferred accepted rejected ; do
git push quagga-gnu.org :refs/heads/volatile/patch-tracking/4/${H}
git push quagga-gnu.org
${H}:refs/heads/volatile/patch-tracking/4/${H}
done
Where quagga-gnu.org is the remote I have defined:
$ git remote -v | grep quagga-gnu
quagga-gnu.org ssh://git.sv.gnu.org/srv/git/quagga.git (fetch)
quagga-gnu.org ssh://git.sv.gnu.org/srv/git/quagga.git (push)
Btw, you havn't carried forward the previous round's deferred branc?
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
God, I ask for patience -- and I want it right now!
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
