git svn - git svn - <file> was not found in commit <hash> -


in middle of pulling down (rather large) svn repo git-svn, encountered following error message (generic info substituted real info):

found possible branch point: svn://server/project/trunk/dir => svn://server/project/branches/branchname, <revision> initializing parent: refs/remotes/branchname@<revision> project/trunk/dir/file not found in commit <hash> (r<revision>) 

i have read in other posts possible "un-fetch" info through tinkering. however, rather not lose history , go forward painlessly possible.

how can git-svn fetch continue?

this means receiving new svn revision modifies file (for reason) not exist in git commit equivalent of parent svn revision. 1 easy way cause inconsistent --ignore-paths (originally there no way configure , had entered on every git-svn command line might fetch). way on svn server end change repository permissions in such way whole subtree of files appears (from perspective) git repository has no history for.

the easiest way past immediate problem , continue git-svn fetch use --ignore-paths (or better svn-remote.svn.ignore-paths config entry) ignore problem part of tree. can away command line argument pass single revision , won't hit problem again until modifies on svn side.

if want recover without --ignore-paths need fix parent revision includes file being modified. wrote git-svn reset "un-fetch" refer less tinkering. can reset svn remote file created can integrate history. won't wipe out working copies, need reparent working branches on new history.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -