From: Andreas Gruenbacher <agruen@suse.de>
To: git@vger.kernel.org
Subject: Merge format documented?
Date: Mon, 23 Mar 2009 04:19:49 +0100 [thread overview]
Message-ID: <200903230419.50000.agruen@suse.de> (raw)
Hello,
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:
$ seq 1 7 > a
$ seq 1 7 | sed -e 's/4/4b/' > b
$ seq 1 7 | sed -e 's/3/3c/' > c
$ diff3 -m c a b
> 1
> 2
> <<<<<<< c
> 3c
> 4
> ||||||| a
> 3
> 4
> =======
> 3
> 4b
> >>>>>>> b
> 5
> 6
> 7
Git's output in this case is:
> 1
> 2
> <<<<<<< this-branch
> 3c
> 4
> =======
> 3
> 4b
> >>>>>>> merged-branch
> 5
> 6
> 7
Does git ever output a ||| section?
Thanks,
Andreas
next reply other threads:[~2009-03-23 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 3:19 Andreas Gruenbacher [this message]
2009-03-23 3:50 ` Merge format documented? Junio C Hamano
2009-03-23 7:18 ` Andreas Gruenbacher
2009-03-23 7:52 ` Junio C Hamano
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=200903230419.50000.agruen@suse.de \
--to=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).