From: "Yann Dirson" <ydirson@linagora.com>
To: "Michael J Gruber" <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git-svn: HEAD pointing to a tag after cloning
Date: Mon, 11 May 2009 16:09:42 +0200 (CEST) [thread overview]
Message-ID: <53308.10.0.0.1.1242050982.squirrel@intranet.linagora.com> (raw)
> 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.
next reply other threads:[~2009-05-11 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 14:09 Yann Dirson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-11 11:08 [BUG] git-svn: HEAD pointing to a tag after cloning Yann Dirson
2009-05-11 11:50 ` Michael J Gruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53308.10.0.0.1.1242050982.squirrel@intranet.linagora.com \
--to=ydirson@linagora.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).