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

git-svn usability

From
David Kågedal <davidk@lysator.liu.se>
Date
Jan 4, 2007, 17:34 UTC
Message-ID
<87fyaqvgoz.fsf@morpheus.local>

I wanted to try out "git svn" and did a "git help svn" and got the man page for git-svn. That page starts out by describing that git-svn only is useful for working with a single svn branch. But then, further down, it describes the commands "multi-init" and "multi-fetch" anyway. Confusing. But I decided to give them a try. But there isn't really any clear description on what the command line should look like when you use multi-init (or any other git-svn command for that matter). So I boldly decided to try to run "git svn help multi-init". You never know, it might tell you something. This is what happened:

  morpheus% git svn help multi-init
  GIT_SVN_ID set to 'trunk' for help/trunk
  Initialized empty Git repository in /home/david/tmp/.git/
  W: --branches/-b not specified
  W: --tags/-t not specified

Not exactly what I wanted. The command-line parser in git-svn is broken since it picks the first argument that looks like a command name.

-- 
David Kågedal
Next: Eric Wong
Message 1 of 8 in “git-svn usability”
  1. David KågedalJan 4, 2007
  2. 1/2 git-svn: make multi-init less confusingEric Wong, Jan 5, 2007
  3. David KågedalJan 5, 2007
  4. Seth FalconJan 5, 2007
  5. David KågedalJan 8, 2007
  6. David KågedalJan 8, 2007
  7. David KågedalJan 8, 2007
  8. 2/2 git-svn: update documentation for multi-{init|fetch}Eric Wong, Jan 5, 2007

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.