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

Re: git svn project shuffle

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 15, 2010, 16:48 UTC
Message-ID
<20101015164811.GA10204@burratino>
In-Reply-To
<AANLkTimxbmk2u=4d1b1LS+GMp9ry__4TtEx5UMJPk4-5@mail.gmail.com>
Hi again,
Christopher Snapp wrote:
> If you remember my old project's trunk has been copied to a
> subdirectory of the new project's trunk.  So, oldproj/trunk is now
> newproj/trunk/oldproj.

Yeah, I was ignoring this part. :) git svn is not really wired for it.

The instructions were meant to also be usable in a case where oldproj and newproj are entirely independent repositories.

> When I do a git svn clone of the newproj I
> would expect it to follow the svn copy that created
> newproj/trunk/oldproj but it doesn't.

If the layout has been relatively stable before, maybe "git svn --no-follow-parent" would give some joy.

Still I would be interested in hearing where the grafting procedure went wrong. If you end up tracking it down to a single step, do please let us know.

Regards, Jonathan

Previous: Christopher Snapp
Message 4 of 4 in “git svn project shuffle”
  1. Christopher SnappOct 4, 2010
  2. Jonathan NiederOct 4, 2010
  3. Christopher SnappOct 13, 2010
  4. Jonathan NiederOct 15, 2010

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.