Created
July 4, 2010 23:39
-
-
Save octaviordz/463865 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
New feature git-svn | |
=================== | |
Problem: When cloning from a svn repository that is corrupted, git-svn fails trying to fetch the revision that | |
is corrupted. | |
Lets explain it with an example: | |
git svn clone http://svn.server.com/project | |
# gits start getting the revisions from the svn server. | |
# when it gets to revision 1234 it fails with the next error | |
File/Path was not found in commit ab123... (r1234) | |
Current work around: Clone from a later revision, for instance. | |
# clone it from revision 1235 doing this git-svn ends without error | |
git svn clone -r1235 http://svn.server.com/project | |
Now you end up with two git repositories one from revision 0 to 1234 and other from revision 1235 to HEAD | |
Desirable feature description:Modify git-svn to have a options like '--skip-errors' that could handle this type of | |
errors. In a way that 'git svn clone --skip-errors http://svn.server.com/project' will result in a repository with | |
all the revisions except those that were corrupted. | |
I hope I made myself clear. | |
P.S. In the mean time does any one know how can you merge those two repositories without affecting git-svn metada. | |
some updates?
It would be useful indeed...
as workaround for some old SVN Repos from us, im use the param -r
git svn clone -s -r1450:HEAD some/svn/repo
to ignore very old commits.
The first git commit after migration contains the last content from commit 1 - 1450
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Desperately needed!
Agreed :)