From: Deskin Miller <deskinm@gmail.com>
Date: Thu, 23 Apr 2009 05:56:27 GMT
Subject: Re: [GIT-SVN] master follows not trunk
Message-ID: <86d4c5e00904222256r157ca34ex8c56c671991e663c@mail.gmail.com>
In-Reply-To: <36ca99e90904220821u3dae67d7jcb6366d7a95dfbd1@mail.gmail.com>

On Wed, Apr 22, 2009 at 08:21, Bert Wesarg <bert.wesarg@googlemail.com> wrote:
> Hi,
>
> it seams so, that git-svn sets the master branch to that svn branch
> which has the highest revision!
>
> I cloned a svn repo today where exactly this happend. I.e. master
> pointed not to the trunk but to the branch with the highest revision.
> After trunk moved forward, a git svn rebase told me that master is up
> to date.
>
> A second clean clone of this repo and master pointed to trunk.
>
> Is this indented?

It's well-known, at any rate, and it's somewhat conceptually
consistent with git, which will use the remote's HEAD for its
currently-checked-out branch upon clone.

Consider also that although your svn repository is well-formed and has
trunk/ tags/ branches/, not all do; or, perhaps someone is interested
in only one branch, or put multiple svn-remote.svn.fetch lines in
.git/config before fetching.  Which svn branch should become master
then?

With that said, you're not the first person to be surprised by this;
I'm sure you could patch git svn to tell you which svn branch it was
checking out.  It'd probably be a pretty simple tweak, but
unfortunately I'm not in a position to do it currently.

Deskin Miller