Show 6 quoted lines
> 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.
I am aware of that. However, nothing seems to prevent svn tags to be mapped to tag refs insead of head refs. Maybe both behaviours could be available, if someone wants to be able to "commit to svn tags" properly from git, but since that is probably not the common case, I would rather see this current behaviour as an option.
But we are going off-topic here. That "feature" of git-svn checking out "the branch on which the last commit was done" is fortunately not being documented in the manpage :). The problem here (distinct from the tag-handling issue) is that you can barely predict what svn remote your master branch will track !
> 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.
Exactly, that would simply be consistent.