From: Junio C Hamano <gitster@pobox.com>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: git@vger.kernel.org
Subject: Re: Merge format documented?
Date: Mon, 23 Mar 2009 00:52:28 -0700 [thread overview]
Message-ID: <7viqm08ymb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200903230818.20044.agruen@suse.de> (Andreas Gruenbacher's message of "Mon, 23 Mar 2009 08:18:19 +0100")
Andreas Gruenbacher <agruen@suse.de> writes:
> On Monday, 23 March 2009 4:50:24 Junio C Hamano wrote:
>> Andreas Gruenbacher <agruen@suse.de> writes:
>> > is the format that git normally uses for indicating merge conflicts in
>> > files (the <<< === >>> markers) documented somewhere? How exactly does
>> > it differ from the diff3 format (<<< ||| === >>>)? Diff3's -m mode seems
>> > to come close to what git does, except that git doesn't produce the |||
>> > section:
>>
>> It is an imitation of output from "merge" program of RCS suite Paul you
>> know maintains ;-)
>
> So it's the same format except that diff3's ||| section isn't shown. I was
> wondering if there are any additional tricks.
No additional tricks.
As far as I can remember, the format was not really chosen, but simply
fell out as a natural consequence of using "merge" rather than "diff3" as
a merge backend (we originally used to invoke "merge" from RCS suite
instead of performing file-level merges ourselves), but we could say we
chose "merge" over "diff3 -m" because the output format should be more
familiar than the diff3-m format with |||, especially to anybody who came
from subversion or CVS background.
next prev parent reply other threads:[~2009-03-23 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 3:19 Merge format documented? Andreas Gruenbacher
2009-03-23 3:50 ` Junio C Hamano
2009-03-23 7:18 ` Andreas Gruenbacher
2009-03-23 7:52 ` Junio C Hamano [this message]
2009-03-23 9:17 ` Johannes Sixt
2009-03-27 16:05 ` Jakub Narebski
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=7viqm08ymb.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=agruen@suse.de \
--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).