Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

error initializing the branch

See original GitHub issue

Initialized empty Git repository in D:/bvkmut/Main/.git/ Fetching from TFS remote ‘default’… C22827 = 97c4058b28b73c187938844f0ba39e945ab53feb Tfs branches found:

$/BVKMut-ES-Tool/Release1.0
$/BVKMut-ES-Tool/Release2.0 => Working on TFS branch : $/BVKMut-ES-Tool/Release1.0 Branches to Initialize successively : -$/BVKMut-ES-Tool/Release1.0 (24171) The name of the local branch will be : Release1.0 error: an error occurs when initializing the branch. Branch is ignored and continuing… => Working on TFS branch : $/BVKMut-ES-Tool/Release2.0 Branches to Initialize successively : -$/BVKMut-ES-Tool/Release2.0 (32751) The name of the local branch will be : Release2.0 error: an error occurs when initializing the branch. Branch is ignored and continuing… => Working on TFS branch : $/BVKMut-ES-Tool/Main Warning: git gc failed! warning: Some Tfs branches could not have been initialized:
$/BVKMut-ES-Tool/Release1.0
$/BVKMut-ES-Tool/Release2.0

Please report this case to the git-tfs developers! (report here : https://github.com/git-tfs/git-tfs/issues/461 ) warning: Some Tfs branches could not have been initialized or entirely fetched due to errors:

$/BVKMut-ES-Tool/Release1.0 =>error:error: Couldn’t fetch parent branch
$/BVKMut-ES-Tool/Release2.0 =>error:error: Couldn’t fetch parent branch

Please report this case to the git-tfs developers! (report here : https://github.com/git-tfs/git-tfs/issues )

Issue Analytics

State:
Created 8 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

pbl2108commented, Feb 5, 2016

I was having the same problem where the main branch was deleted and started from scratch, and starting from the first changeset after the delete (e.g. --changeset==12345) solved the problem for me. The full command looked something like this:

> git tfs clone https://tfs.codeplex.com:443/tfs/Collection $/project/trunk --changeset=12345 --with-branches

1reaction

elangelocommented, Sep 24, 2015

I have detected what is probably the problem. At a certain moment the developer decided to delete everything (so also the Main branch) and start from scratch. He started again from c22829. So i could fix my problem with a simple --change-set=22829 to skip all changes before that 😃 Is there anything in this case that might justify further research?