OSPF stuck in 2-way state

Ondrej Zajicek santiago at crfreenet.org
Tue Oct 8 13:47:29 CEST 2019


On Tue, Oct 08, 2019 at 09:45:54AM +0000, Kenth Eriksson wrote:
> On Tue, 2019-10-08 at 11:34 +0200, Ondrej Zajicek wrote:
> The broken 2.0.6 tag I had locally was
> 3a22a6e858cd703d254ab331183ccd56fe195c6b, which is only six commits
> after 2.0.4. But I have now deleted that erroneous tag and fetched
> again. 
> 
> Thanks for confirming my suspicion about a faulty 2.0.6 tag, but next
> time please try to avoid rebasing/rewriting git history...  I recall I
> had a similar problem when you moved from github to gitlabs.

I agree that we should avoid rebasing/rewritting git history, but this
issue was not intentional rebasing, but fixing badly generated tag.
If we had kept the old broken tag v2.0.6 and had generated a new tag
v2.0.6-fixed, that would have likely caused much more confusion.

BTW, we did not move from Github to Gitlab. We never used Github. Before
Gitlab, we used regular git server.

-- 
Ondrej Santiago Zajicek


More information about the Bird-users mailing list