From: Junio C Hamano <gitster@pobox.com>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [RFC] (reverse) combined diff conflict style
Date: Thu, 18 Feb 2010 12:34:31 -0800 [thread overview]
Message-ID: <7v1vgi8eqw.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 1266521789-3617-1-git-send-email-bert.wesarg@googlemail.com
Bert Wesarg <bert.wesarg@googlemail.com> writes:
> ----- output ----
>
> 1
> <<<<<<<
> -2
> - 3
> >>>>>>>
> 4
>
> ------ end ------
>
> As you can see, the conflict region is way smaller as the diff3 one, but
> keeps all information.
>
> I'm not doing much merges myself, so there are probably people out there who
> can better judge the usefulness of this style.
As a format to review conflicted regions in a pager, this might be a good
alternative representation.
But I doubt I would want to use this as a way for "git merge", "git am -3"
and their friends to write a half-merged result out to the work tree for
me to resolve. With either --conflict=merge or --conflict=diff3, it is
easy to pick lines from either side (you remove what is not needed in the
final result), but with this format you always have to not just pick but
remove the change marker at the beginning from the "these are good, I'd
use them" lines. And you have to do so for every single line you reuse
from either side.
next prev parent reply other threads:[~2010-02-18 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 19:36 [RFC] (reverse) combined diff conflict style Bert Wesarg
2010-02-18 20:34 ` Junio C Hamano [this message]
[not found] ` <36ca99e91002181243y371ce2f5i7136d8fbe6837b6b@mail.gmail.com>
[not found] ` <7vocjlx056.fsf@alter.siamese.dyndns.org>
2010-02-19 7:15 ` Bert Wesarg
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=7v1vgi8eqw.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=srabbelier@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 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).