From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: Union diff
Date: Sun, 09 Apr 2006 02:45:37 -0700 [thread overview]
Message-ID: <7vslonaxq6.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060326102100.GF18185@pasky.or.cz> (Petr Baudis's message of "Sun, 26 Mar 2006 12:21:00 +0200")
Petr Baudis <pasky@ucw.cz> writes:
> Now, the -c option documentation says:
>
> It shows the differences from each of the parents to the merge
> result simultaneously, instead of showing pairwise diff between
> a parent and the result one at a time, which '-m' option output
> does.
>
> This sounds as exactly what I want. Well, the only problem is that the
> same diff command as above with -c option added produces no diff at all,
> just the header and commit messages. Did I misunderstand the -c
> description and does it do something different?
The --combined diff option is to show merges more sensibly than
plain -m option. Now, the definition of "sensible" is to say
that a merge is not interesting if it takes a version from one
of the parents. The paths whose results do not match any of the
parents' version are deemed interesting and are shown.
I think you could tweak and give an option to intersect_paths()
in combine-diff.c, so that paths that match one of the parents
are also included in the output. I haven't thought about it too
much, but my gut feeling is it would not be very involved
change.
next prev parent reply other threads:[~2006-04-09 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 10:21 Union diff Petr Baudis
2006-04-09 9:45 ` Junio C Hamano [this message]
2006-04-09 13:43 ` [PATCH] Improve the git-diff-tree -c/-cc documentation Petr Baudis
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=7vslonaxq6.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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