From: "Shawn O. Pearce" <spearce@spearce.org>
To: Adam Majer <adamm@zombino.com>
Cc: git@vger.kernel.org
Subject: Re: git and appending merge commits
Date: Mon, 26 May 2008 00:51:36 -0400 [thread overview]
Message-ID: <20080526045136.GC30245@spearce.org> (raw)
In-Reply-To: <483A300E.6090104@zombino.com>
Adam Majer <adamm@zombino.com> wrote:
...
> 5. append master merge changeset
>
> #5 results in "messsed up" diffs
>
> For an example of such a mess up please see,
>
> http://git.debian.org/?p=collab-maint/mrtg.git;a=commitdiff;h=a8bc78ffd6d51ab09a791fa97e25f57b60eecd06
>
> It appears that the tool generates a patch to a patch and displays that
> instead of the appended merge diff which is what I would have expected..
>
> Is current output by design?
Yes, it is by design. This is a feature of Git that very few
(if any) other systems have.
What you are seeing here is a combined diff. It is a diff of the
final output of the merge against its two parents (the two branches
that were merged together). Places where both a "++" or "--" prefix
a line indicate a place where the merge commit adds something that
is not in either parent. This is stuff that the merge author edited
himself/herself during the merge.
If you had not amended the merge, you would have seen a less
interesting diff here, as the combined diff output tries to
avoid showing trivial changes.
--
Shawn.
next prev parent reply other threads:[~2008-05-26 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 3:35 git and appending merge commits Adam Majer
2008-05-26 4:51 ` Shawn O. Pearce [this message]
2008-05-26 4:59 ` Junio C Hamano
2008-05-26 6:39 ` Adam Majer
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=20080526045136.GC30245@spearce.org \
--to=spearce@spearce.org \
--cc=adamm@zombino.com \
--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).