From: Junio C Hamano <junkio@cox.net>
To: David Ho <davidkwho@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-diff-tree rename detection for single file
Date: Tue, 18 Oct 2005 13:50:54 -0700 [thread overview]
Message-ID: <7vu0fepn0x.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <4dd15d180510181256i1c5a82d9ld62acaedb493cf71@mail.gmail.com> (David Ho's message of "Tue, 18 Oct 2005 15:56:06 -0400")
David Ho <davidkwho@gmail.com> writes:
> I have a small suggestion to make the diff of a renamed file a bit
> more meaningful. I have a file that is renamed-edited and commited.
> git-diff-tree -M -p <commit> shows one result and git-diff-tree -M -p
> <commit> <filename> shows another. If they both show a rename
> occurred then I think the single file git-diff-tree will be more
> useful.
Sorry, this has vetoed by Linus long time ago. The <filename>
restricts the paths being passed to the diff machinery upfront,
so once you say <filename>, the rename detection will see only
that path and nothing else to compare and guess which other file
that file in question is a copy of.
next prev parent reply other threads:[~2005-10-18 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 19:56 git-diff-tree rename detection for single file David Ho
2005-10-18 20:50 ` Junio C Hamano [this message]
2005-10-19 2:45 ` Junio C Hamano
2005-10-19 3:12 ` Linus Torvalds
2005-10-19 5:20 ` Junio C Hamano
2005-10-19 16:04 ` Nicolas Pitre
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=7vu0fepn0x.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=davidkwho@gmail.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