my svn structure is trunk/branches/tags based, although I don't need it
like that in git.
lets say I am pulling from
https://svn.isr.hp.com/rg0202/alm/horizon/trunk(since I need only
trunk's history and not all other branches). that gives
me history only as far as May 2012, when this branch was created. I would
like it to go further back as I see it in svn when I ask to see older
this branch came out from another branch, which came from another and so
on. I wanted to to fetch from a certain revision somewhere along this path.
what you are saying is that I need to do it in chunks and stitch it
together to a one big happy git repository afterward ? isn't any other
clever way for this ?
is pulling with -s will give me any advantage towards achieving this ?
On Thu, Jul 19, 2012 at 8:55 AM, Thomas Ferris Nicolaisen
> 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
> 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, here:
> 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
> trunk/branches/tags layout?
> 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
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at