From: "Guilhem Bonnefille" <guilhem.bonnefille@gmail.com>
To: "Steven Grimm" <koreth@midwinter.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn and local only topic branch
Date: Thu, 3 May 2007 13:24:01 +0200 [thread overview]
Message-ID: <8b65902a0705030424o4bd63435h143ba36ca5166902@mail.gmail.com> (raw)
In-Reply-To: <4638E127.4010303@midwinter.com>
On 5/2/07, Steven Grimm <koreth@midwinter.com> wrote:
> In his reply to my script, Junio correctly pointed out that all this
> fiddling really ought to be happening in git-svn itself; it ought to
> know that you've done a merge and should record that fact directly in
> the metadata for 4' rather than treating it as a single-parent commit.
> If you do the above a zillion times you'll end up with a huge grafts
> file which is not so clean. But as a stopgap measure, this does work
> adequately.
Yes, it's seems just fine. Thanks for the tips.
I'm not aware with the internal Git's features. As grafts seems to be
a quick hack, is it posible to imagine that, after git-svn rewrited 4
in 4', an other tool rewrites (completly) the commit to produce a 4"
with 2 parents?
--
Guilhem BONNEFILLE
-=- #UIN: 15146515 JID: guyou@im.apinc.org MSN: guilhem_bonnefille@hotmail.com
-=- mailto:guilhem.bonnefille@gmail.com
-=- http://nathguil.free.fr/
prev parent reply other threads:[~2007-05-03 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 16:40 git-svn and local only topic branch Guilhem Bonnefille
2007-05-01 16:45 ` Adam Roben
2007-05-01 17:30 ` Guilhem Bonnefille
2007-05-01 18:29 ` Andy Parkins
2007-05-02 19:06 ` Steven Grimm
2007-05-03 11:24 ` Guilhem Bonnefille [this message]
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=8b65902a0705030424o4bd63435h143ba36ca5166902@mail.gmail.com \
--to=guilhem.bonnefille@gmail.com \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.com \
/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).