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

Re: [git-svn] [FEATURE-REQ] track merges from git

From
BDBryan Donlan <bdonlan@gmail.com>
Date
Aug 26, 2009, 19:06 UTC
Message-ID
<3e8340490908261206xc4156c4mb46e4c7de264df11@mail.gmail.com>
In-Reply-To
<4A9565ED.4010608@cam.ac.uk>
On Wed, Aug 26, 2009 at 12:42 PM, Ximin Luo<xl269@cam.ac.uk> wrote:
Show 28 quoted lines
> Hi,
>
> I'm have 2 separate svn projects from googlecode imported into a single git
> repo. One is a semi-fork of the other, so I thought I'd be able to use git's
> merge feature to repeatedly merge from the mother project (and possibly vice
> versa too).
>
> However, this doesn't happen. I "git pull" and this works fine, but when I "git
> svn dcommit" back into svn, this rewrites my git history and it loses track of
> the merge (and next time I try to pull, the same conflicts appear).
>
> For now I just have a .git/info/grafts, but this doesn't get exported anywhere,
> so if other people "git svn clone" from svn, or "git clone" from my git repo,
> they don't get the merge information.
>
> It would be nice if git-svn saved the merge info somewhere instead of getting
> rid of it. #git tells me this is impossible at the moment, hence the mail.
> Relevant parts of the convo are pasted below.
>
> I understand if this is a low priority, but I don't think it would be a major
> PITA to implement (some suggestions are listed in the convo log). And it'd be
> useful for people converting from svn to git.
>
> Thanks for your time.
>
> X
>
> P.S. please don't troll me.

For the particular use case you have, I suspect svk would be a better tool for merging between those two projects... git-svn is rather specifically designed to only deal with a single upstream repository, you see, and it isn't very easy to change this to accept multiple repos.

Previous: Ximin LuoNext: Eric Wong
Message 2 of 7 in “[git-svn] [FEATURE-REQ] track merges from git”
  1. Ximin LuoAug 26, 2009
  2. Bryan DonlanAug 26, 2009
  3. Eric WongSep 5, 2009
  4. Ximin LuoSep 6, 2009
  5. Jakub NarebskiSep 5, 2009
  6. Ximin LuoAug 26, 2009
  7. Ximin LuoAug 26, 2009

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.