Bert Wesarg [off-list ref] 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?
Yes it was intended. It was once the case that several repositories I
tracked had work done almost exclusively in branches and trunk could've
been months/years behind and worthless.
However, this issue has come up many times now so maybe setting
master==trunk if trunk exists (sometimes it does not)...
Any objections?
--
Eric Wong