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

Importing a strange svn repo layout w/ git-svn

From
Asheesh Laroia <asheesh@asheesh.org>
Date
Apr 30, 2008, 04:20 UTC
Message-ID
<alpine.DEB.1.00.0804300011390.29172@rose.makesad.us>

I'm working on cloning the MediaWiki (a common wiki engine, used to power e.g. wikipedia.org) Subversion tree using git-svn. It has this peculiar layout:

$BASE/trunk/phase3 is the project trunk $BASE/tags/TAG_NAME/phase3 is the tag TAG_NAME $BASE/branches/BRANCH_NAME/phase3 is the branch BRANCH_NAME

"phase3" is not the only directory in e.g. http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_12/ - there is also an "extensions" directory, a snapshot of MediaWiki extensions for that branch. But those are truly separate projects with separate contributors, and have to be installed in a separate place.

When cloning other svn repositories, I saw that strange layouts can be accommodated by just cloning the trunk. But in this case,

I considered using git-svn like this:

$ git svn http://svn.wikimedia.org/svnroot/mediawiki/ -t tags/phase3/ -b branches/phase3/ -T trunk/phase3/

But that wouldn't be correct, since it wouldn't actually pick up the tag or branch names!

Is there a way to get git-svn to handle this situation? Perhaps git-svn has a "suffix $DIR to the repository URL" option that I missed. If not, is it conceivable it could?

-- Asheesh.
-- 
Beauty?  What's that?
 		-- Larry Wall in <199710221937.MAA25131@wall.org>
Next: Paolo Bonzini
Message 1 of 3 in “Importing a strange svn repo layout w/ git-svn”
  1. Asheesh LaroiaApr 30, 2008
  2. Paolo BonziniApr 30, 2008
  3. Asheesh LaroiaApr 30, 2008

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.