From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Replace rebase with filtering
Date: Tue, 16 Jan 2007 16:22:19 -0500 [thread overview]
Message-ID: <20070116212219.GA29434@spearce.org> (raw)
In-Reply-To: <eojf73$1f4$1@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> wrote:
> Steven Grimm wrote:
> > Okay, great, that is certainly an improvement over what I thought was
> > happening. But it won't work if you had to manually resolve a conflict
> > during the rebase, yes? In that case the diffs would presumably not match.
>
> Then git-rerere would help, I think.
No, because rerere only helps to recall a prior conflict resolution.
Here Steven is talking about having rebase intelligently realize that
the upstream has accepted a patch, but did so by modifying it first.
There really isn't a solution to the problem.
pg tried to do this by applying several patches at once until
something matched. If the upstream fixed a line like "a=b" to
be "a = b" then this would *never* match, and pg would abort.
StGIT runs the patches backwards. A much smarter approach then
what pg tried to do, but again, "a = b" would never match.
--
Shawn.
next prev parent reply other threads:[~2007-01-16 21:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 2:41 [RFC] Replace rebase with filtering Steven Grimm
2007-01-16 11:18 ` Johannes Schindelin
2007-01-16 19:20 ` Steven Grimm
2007-01-16 19:43 ` Steven Grimm
2007-01-16 20:35 ` Johannes Schindelin
2007-01-16 20:40 ` Steven Grimm
2007-01-16 21:14 ` Jakub Narebski
2007-01-16 21:22 ` Shawn O. Pearce [this message]
2007-01-16 21:23 ` Johannes Schindelin
2007-01-16 21:20 ` Johannes Schindelin
2007-01-16 21:49 ` Jakub Narebski
2007-01-16 22:31 ` Brian Gernhardt
2007-01-16 22:51 ` Johannes Schindelin
2007-01-16 22:53 ` Junio C Hamano
2007-01-16 22:57 ` Johannes Schindelin
2007-01-17 22:21 ` Steven Grimm
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=20070116212219.GA29434@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.