Note that git-svn will not follow history outside the paths you specify for
it. I believe it is restricted to a trunk and branches in a set location.
If at some point, the whole trunk/branches/tags was moved to a different
place in the repository, you have to splice together two git-svn clones to
acquire the entire history: one clone for history before the move, and
another clone for history after the move.
I've created a screencast that demonstrates the above splicing, or grafting
as it is called in Git terminology,
If you don't specify a -r range for git-svn, it will check all revisions
(for the given path).
Furthermore, it doesn't look like you specified -s or --stdlayout when
running git-svn clone, nor did you specify --branches. This means that
git-svn will only get history for the path you provided, and ignore any
branches or tags adjacent to it.
Again, how is the structure of your repository? Is it a standard
On Thursday, July 19, 2012 7:26:09 AM UTC+2, Gabby Romano wrote:
> first I used the regular git svn clone command - git svn clone <svn path>.
> then tried with -r<rev num>:HEAD but that didn't work for me
> either. probably tried a few more options but to no avail. I am sure git
> knows how to "follow" the history despite the branching but didn't find the
> right way to do it.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at