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

Re: [PATCH] contrib/git-svn: use refs/remotes/git-svn instead of git-svn-HEAD

From
N'Nicolas Vilz 'niv' <nicolas@vilz.de>
Date
Mar 2, 2006, 21:17 UTC
Message-ID
<62157.84.163.95.215.1141334223.squirrel@mail.geht-ab-wie-schnitzel.de>
In-Reply-To
<20060302055831.GA16600@localdomain>
Show 7 quoted lines
> After reading a lengthy discussion on the list, I've come to the
> conclusion that creating a 'remotes' directory in refs isn't
> such a bad idea.
>
> You can still branch from it by specifying remotes/git-svn (not
> needing the leading 'refs/'), and the documentation has been
> updated to reflect that.
i got stuck in that.

git-svn does the remotes/svn-git reference good, git pull hasn't recognized it, yet. So i had to do a symlink from .git/refs/remotes to .git/refs/heads/ to do the git pull...

then i got a bit stuck because of conflicts.... which i resolved (thank god).

the third thing is that the git-svn commit command does deletions of certain files very often, when i commit some patches i pulled into my private-talk-to-svn-branch. in on of the next commits the same files are added again.. but i thought "o my god, i am screwed", when i saw the scheduled deletions the first time... that is a bit confusing for the users.

so in conclusion, i think, you should teach git pull to recognize refs/remotes as heads to be pulled from (not to be pulled at)...

btw, i like the visualization of the remotes-refs in gitk.
Nicolas
Previous: Eric Wong
Message 3 of 3 in “contrib/git-svn: use refs/remotes/git-svn instead of git-svn-HEAD”
  1. contrib/git-svn: use refs/remotes/git-svn instead of git-svn-HEADEric Wong, Mar 2, 2006
  2. git-branch: add -r switch to list refs/remotes/*Eric Wong, Mar 2, 2006
  3. Nicolas Vilz 'niv'Mar 2, 2006

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.