git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[BUG] git-svn: HEAD pointing to a tag after cloning

From
YDYann Dirson <ydirson@linagora.com>
Date
May 11, 2009, 11:08 UTC
Message-ID
<37678.10.0.0.1.1242040118.squirrel@intranet.linagora.com>

The following happens with git 1.6.3. For some reason git-svn sets HEAD to the wrong branch. Not sure what happens here, $self->full_url seems to be used for a wrong purpose somewhere in the code.

(you can see a commit on the "tag" branch, which got committed at the wrong place because the user did not notice that HEAD was not pointing to the correct branch)

$ git svn clone --stdlayout svn://xxxx/at-remote test
[....]
Successfully followed parent
r3287 = 08b210cf2e97caeb6d431a4a0bc594702aa9c6d2 (tags/luciole-2.0.4)
Found possible branch point: svn://xxxx/at-remote/trunk =>
svn://xxxx/at-remote/tags/luciole-2.0.5, 3352
Found branch parent: (tags/luciole-2.0.5)
ddff7cedbd1d66c836153606db1f80ad3ce6b00d
Following parent with do_switch
Successfully followed parent
r3367 = 35b21f3f8e206c391f09a788ba9cb6b35f21752d (tags/luciole-2.0.5)
        M       at-remote
r3652 = faeb3bab02016b23a7fb7256bbabea305f599022 (tags/luciole-2.0.5)
Checked out HEAD:
  svn://xxxx/at-remote/tags/luciole-2.0.5 r3652
$
Next: Michael J Gruber
Message 1 of 2 in “[BUG] git-svn: HEAD pointing to a tag after cloning”
  1. Yann DirsonMay 11, 2009
  2. Michael J GruberMay 11, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.