If fixed means “rebased the whole
volatile/patch-tracking/6/proposed/ff branch”, then yes.
PLEASE, PLEASE do not rebase any public branches.
(Every Git doc makes it clear on how bad this is…)
I would rather abandon the branch and create a new one (i.e. a “6a”
branch)
Completely screwed my testing as commits ID’s disappeared. I depend on
predictable
commit IDs for my testing (and retesting)
- Martin
On 17 Feb 2016, at 4:27, Donald Sharp wrote:
Martin -
We've fixed the branch names in github. Sorry for the breakage.
doanld
On Tue, Feb 16, 2016 at 10:29 PM, Martin Winter <
[email protected]> wrote:
I suddenly see 2 branches:
volatile/patch-tracking/6/proposed/ff
and
remotes/quagga-gnu/volatile/patch-tracking/6/proposed/ff
Sadly, they seem not to be in sync either. (i.e., the last commit
from Lou
Berger “bgpd: Fix graceful restart capability minsize…”
is in “volatile/patch-tracking/6/proposed/ff” only, but otherwise
the
“remotes/quagga-gnu/volatile/patch-tracking/6/proposed/ff”
seems to have newer commits (by date)
Could some maintainer please look into this and comment? Looks like
something went badly wrong to me…
- Martin
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
