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

Re: [PATCH] SVN import: Use one log call

From
Matthias Urlichs <smurf@smurf.noris.de>
Date
Nov 30, 2005, 08:34 UTC
Message-ID
<20051130083436.GZ20418@kiste.smurf.noris.de>
In-Reply-To
<7vwtiqwoy7.fsf@assigned-by-dhcp.cox.net>
Hi,
Junio C Hamano:
Show 8 quoted lines
> 	$ git svnimport -T main/sources \
> 	    http://127.0.0.1/svn/private/main/sources/photocat
> 
> seems to be doing something.  But I do not understand why.  How
> did you decide "-T main/sources" is good for my case while "-T
> main/brltty" is good for Nicolas?  I would have guessed you may
> say "-T main" for Nicolas, dropping the last path component.
> 

What git-svnimport does right now is rather simple. It pulls the log from the SVN URL, drops everything that does not have a prefix of either of the -t tags -T trunk -b branches options. The prefix is then thrown away. If it's a trunk, import the rest to the "origin" branch; otherwise remove the next path component and use that as either the branch name or the tag name.

The point is that the picture in the SVN manual is incomplete. There's not just a branches/ subdirectory alongside the trunk/ one; trunk/ directly contains the project's files, while branches/ contains subdirectories which are named for the branch, and *they* contain the files.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
If you're looking ahead long-term, and what you see looks like
science fiction, it might be wrong. But if it doesn't look like
science fiction, it's definitely wrong...
		-- Christine Peterson,
Previous: Junio C Hamano
Message 7 of 7 in “SVN import: Use one log call”
  1. SVN import: Use one log callMatthias Urlichs, Nov 29, 2005
  2. Junio C HamanoNov 29, 2005
  3. Matthias UrlichsNov 30, 2005
  4. Nicolas PitreNov 30, 2005
  5. Matthias UrlichsNov 30, 2005
  6. Junio C HamanoNov 30, 2005
  7. Matthias UrlichsNov 30, 2005

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.