On Wed, Apr 22, 2009 at 08:21, Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html