From: Johannes Sixt <j.sixt@viscovery.net>
To: git@vger.kernel.org
Subject: Re: Newbie question regarding 3way merge order.
Date: Tue, 03 Feb 2009 08:21:24 +0100 [thread overview]
Message-ID: <4987F074.9040506@viscovery.net> (raw)
In-Reply-To: <87wsc8aenx.fsf@gigli.quasi.internal>
Again: Don't set Mail-Followup-To and keep the Cc list if you want to
communicate efficiently on this list.
Raimund Berger schrieb:
> Are you sure you're not making assumptions about "obvious" manual
> resolutions? E.g. I can't quite see how A+B, which is
>
> g(a)----
> / \
> f(a) g(a)f(b) or f(a)f(b) ???
> \ /
> f(a)f(b)
>
> would not be flagged as a conflict regarding f(a) vs. g(a).
My introductory sentence was probably not clear enough. I meant:
mergebase A B A+B
f g f g
( ( ( (
a a a a
) ) ) )
f f
( (
b b
) )
There is no conflict in A+B. But strctly speaking, this could be regarded
as an ambiguous merge since the change f->g could be applied to two
places. But if context is taken into consideration, then there is no
conflict in practice.
> And that's why I specifically "limited" my equality relation to
> automatic resolutions, to simplify the discussion and deal with kind of
> minimum requirements first. I didn't even mention that originally
> because I felt it was so obvious.
Yes, it was so obvious, that I thought my statement about "colums are
lines" and "saving vertical space" were obvious, too.
-- Hannes
next prev parent reply other threads:[~2009-02-03 7:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:25 Newbie question regarding 3way merge order Raimund Berger
2009-01-30 11:37 ` Raimund Berger
2009-01-30 17:31 ` Sitaram Chamarty
2009-01-30 19:09 ` Raimund Berger
2009-01-31 0:32 ` Sitaram Chamarty
2009-01-31 13:26 ` Raimund Berger
2009-01-31 21:45 ` Nanako Shiraishi
2009-02-01 14:13 ` Raimund Berger
2009-02-01 19:22 ` Junio C Hamano
2009-02-02 1:50 ` Sitaram Chamarty
2009-02-02 14:58 ` Raimund Berger
2009-02-02 16:10 ` Johannes Sixt
2009-02-02 18:15 ` Raimund Berger
2009-02-03 7:21 ` Johannes Sixt [this message]
2009-01-31 0:57 ` Nanako Shiraishi
2009-01-31 13:14 ` Raimund Berger
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=4987F074.9040506@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
/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).