From: Johannes Sixt <j6t@kdbg•org>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: [RFD] annnotating a pair of commit objects?
Date: Thu, 03 Jan 2013 11:23:38 +0100 [thread overview]
Message-ID: <50E55C2A.1090204@kdbg.org> (raw)
In-Reply-To: <7vr4m2ycij.fsf@alter.siamese.dyndns.org>
Am 03.01.2013 08:03, schrieb Junio C Hamano:
> The intended use case is to "go beyond rerere". Given a history of
> this shape:
>
> o---o---o---I mainline
> /
> O---o---X---o---A topic A
> \
> o---Y---o---o---B topic B
>
> Suppose in the original O we had a function "distimmed_doshes()" to
> tell if doshes are already distimmed, with some call sites. On the
> branch leading to A, at commit X, this function was renamed to
> "doshes_are_distimmed()", and all existing call sites were adjusted.
> On the side branch leading to B, however, at commit Y, a new call
> site to the old function was added in a file that was not touched
> between O..A at all.
>
> When merging either the topic A or the topic B (but not both) to the
> integration branch that did not touch this function or use of it, no
> special care needs to be taken, but when merging the second topic
> after merging the other one, we need to resolve a semantic conflict.
> Namely, the callsite to "distimmed_doshes()" introduced by commit Y
> needs to be adjusted to call "doshes_are_distimmed()" instead.
I guess this issue comes up when you rebuild pu. Perhaps you (and other
integrators with a similar workflow) are sufficiently served with
something that resembles rebase -p --first-parent, as proposed here:
http://thread.gmane.org/gmane.comp.version-control.git/198125/focus=198483
(A proposal of the same idea appeared already years earlier:
http://thread.gmane.org/gmane.comp.version-control.git/62782/focus=62794
but its implementation only re-did the merge, which would not help your
case.)
-- Hannes
prev parent reply other threads:[~2013-01-03 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 7:03 [RFD] annnotating a pair of commit objects? Junio C Hamano
2013-01-03 8:14 ` Jeff King
2013-01-03 9:59 ` Michael Haggerty
2013-04-05 19:36 ` Antoine Pelisse
2013-04-06 7:55 ` Michael Haggerty
2013-01-03 10:23 ` Johannes Sixt [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=50E55C2A.1090204@kdbg.org \
--to=j6t@kdbg$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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