From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: David Ho <davidkwho@gmail.com>, git@vger.kernel.org
Subject: Re: git-diff-tree rename detection for single file
Date: Tue, 18 Oct 2005 22:20:21 -0700 [thread overview]
Message-ID: <7virvuhylm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0510182004100.3369@g5.osdl.org> (Linus Torvalds's message of "Tue, 18 Oct 2005 20:12:43 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> See what I'm saying?
> ...
> The performance impact of pruning the pathnames _before_ diffing them was
> absolutely staggering. You couldn't reasonably do a "git-whatchanged -p"
Yes, I understood and agreed to that logic on May 27th. That's
why the message you are responding said we could add a new flag,
to give the choice to the user to accept full-tree scan.
The "diff-tree --stdin that follows rename history" example
might want to have some change in either the core side of diff,
or in the rev-list. It may help to have both. I still haven't
thought through the issues.
BTW, I really liked your example that piped multiple diff-trees
together. That is a neat trick.
next prev parent reply other threads:[~2005-10-19 5:20 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
2005-10-19 2:45 ` Junio C Hamano
2005-10-19 3:12 ` Linus Torvalds
2005-10-19 5:20 ` Junio C Hamano [this message]
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=7virvuhylm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=davidkwho@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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