From: Brian Gernhardt <benji@silverinsanity.com>
Date: Mon, 30 Jun 2008 20:57:07 GMT
Subject: Re: how does git svn work
Message-ID: <02EDA057-6DE9-4038-ACDA-8763BE0A0D0C@silverinsanity.com>
In-Reply-To: <200806302157.32828.thomas@koch.ro>


On Jun 30, 2008, at 3:57 PM, Thomas Koch wrote:

> In particular I want to follow the repository at:
> http://pubsvn.ez.no/nextgen/
>
> The layout is like
> /trunk
> /stable
>  |- 4.0
>  |- 3.9
>  |- 3.8
>  ...
> /releases
>  |- 4.0
>  |- 4.0r1
>  |- 3.9
>  |- 3.9r1
>  |- 3.9r2
>
>
> I do not know, whether git-svn can create branches automatically for
> each directory under /stable and one main branch for trunk or  
> whether I
> need to create one svn-remote definition for every svn directory I  
> want
> to track.

I'm not sure what commands git-svn uses, but it looks like the  
following command should work:

git svn clone --trunk=trunk --tags=releases --branches=stable http://pubsvn.ez.no/nextgen/ 
  nextgen

That should create a nextgen git repository with a master branch  
following SVN stable, and automatically grabbing anything under stable  
or releases as a new branch.  (I actually marked releases as a tag but  
I think git-svn treats them as branches, since they can change on the  
SVN side.)

~~ Brian