svn allows you to commit to tags as if they were branches - indeed they
are branches just as much as svn branches are branches.
Therefore, git-svn represents svn tags as git remote branches (not
tags). After the clone is done, git-svn checks out the branch on which
the last commit was done.
So, git-svn is doing as it should, under the restrictions that svn puts
on its operations.
One may argue that master should point to trunk (for --stdlayout)
instead after git svn clone, just like master points to master after git
clone. But which one is "the correct branch"? I would claim that the
client cannot know and there should be no master (maybe a detached head
with the last commit, i.e. HEAD) but last I tried I remained a
1-person-minority ;)
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html