From: Mike Hommey <mh@glandium.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git rebase -s ours
Date: Mon, 3 Mar 2008 07:55:21 +0100 [thread overview]
Message-ID: <20080303065521.GA18152@glandium.org> (raw)
In-Reply-To: <20080303054126.GB24210@coredump.intra.peff.net>
On Mon, Mar 03, 2008 at 12:41:26AM -0500, Jeff King wrote:
> On Sun, Mar 02, 2008 at 01:48:48PM +0100, Mike Hommey wrote:
>
> > I don't have a workflow in mind, but I have expectations: considering
> > the documentation, I would expect git rebase -s ours to do what git
> > filter-branch can do with grafts.
>
> I'm not sure I follow. Can you elaborate?
Starting with a history like this:
G---H
/
A---B---C---D---E---F
Where A, B, C, ... are *trees*, not commits, the expected result would
be
A---B---C---D---E---F---G---H
This is what might happen with git-filter-branch if you graft G to F. (I
don't know if it actually works in cases where the grafted commit had a
parent, originally)
Mike
next prev parent reply other threads:[~2008-03-03 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 11:17 [RFC] git rebase -s ours Mike Hommey
2008-03-02 1:05 ` Jeff King
2008-03-02 12:48 ` Mike Hommey
2008-03-03 5:41 ` Jeff King
2008-03-03 6:55 ` Mike Hommey [this message]
2008-03-03 7:03 ` Jeff King
2008-03-03 7:04 ` Mike Hommey
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=20080303065521.GA18152@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).