From: Bryan Donlan <bdonlan@gmail.com>
To: Ximin Luo <xl269@cam.ac.uk>
Cc: git@vger.kernel.org
Subject: Re: [git-svn] [FEATURE-REQ] track merges from git
Date: Wed, 26 Aug 2009 15:06:14 -0400 [thread overview]
Message-ID: <3e8340490908261206xc4156c4mb46e4c7de264df11@mail.gmail.com> (raw)
In-Reply-To: <4A9565ED.4010608@cam.ac.uk>
On Wed, Aug 26, 2009 at 12:42 PM, Ximin Luo<xl269@cam.ac.uk> wrote:
> 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.
next prev parent reply other threads:[~2009-08-26 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 16:42 [git-svn] [FEATURE-REQ] track merges from git Ximin Luo
2009-08-26 19:06 ` Bryan Donlan [this message]
[not found] ` <4A95A032.3000801@cam.ac.uk>
2009-08-26 20:55 ` [git-svn] [BUG] merge-tracking inconsistencies; Was: " Ximin Luo
2009-08-26 21:13 ` Ximin Luo
2009-09-05 8:03 ` [git-svn] " Eric Wong
2009-09-06 22:15 ` Ximin Luo
2009-09-05 9:23 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e8340490908261206xc4156c4mb46e4c7de264df11@mail.gmail.com \
--to=bdonlan@gmail.com \
--cc=git@vger.kernel.org \
--cc=xl269@cam.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).