From: Junio C Hamano <junkio@cox.net>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: git-diff-tree --cc on the dodecapus
Date: Sat, 04 Feb 2006 05:01:22 -0800 [thread overview]
Message-ID: <7vy80rwa59.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <17380.37855.117313.631961@cargo.ozlabs.ibm.com> (Paul Mackerras's message of "Sat, 4 Feb 2006 22:45:35 +1100")
Paul Mackerras <paulus@samba.org> writes:
> Junio,
>
> When I use git diff-tree --cc on Len's dodecapus merge (9fdb62af), the
> first diff hunk that it shows is this:
Yeah, I noticed it too, and you described how that happens quite
well. The algorithm is simplistic and improvement patches are
welcome.
prev parent reply other threads:[~2006-02-04 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 11:45 git-diff-tree --cc on the dodecapus Paul Mackerras
2006-02-04 13:01 ` Junio C Hamano [this message]
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=7vy80rwa59.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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