From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
Abhijit Menon-Sen <ams@toroid.org>,
Pierre Habouzit <madcoder@debian.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: absurdly slow git-diff
Date: Sat, 08 Nov 2008 13:02:52 -0800 [thread overview]
Message-ID: <7vr65maq2r.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0811071554590.3468@nehalem.linux-foundation.org> (Linus Torvalds's message of "Fri, 7 Nov 2008 15:57:23 -0800 (PST)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> Junio, the time difference is quite big for Abhijit's admittedly odd
> test-case:
> ...
> with no difference in output.
In git.git history, "git-whatchanged -m -p -1" gives different output for
the following commits, with and without the patch:
c0e9892637e8144f10f2c408e276a470520f3601
d6b3e3a33f71910526ccf80af6c13a230363cd89
cecb98a9c3ed9271b0974bb6d7edbcf16e8a68f3
ce18135d862b5dbc731d203b27c279529e58b54b
36b5b3c65948694d9a92de5a17f2b97c3cd84879
767e130915015f897fb87b939843b4882212574b
927a503cd07718ea0f700052043f383253904a56
I've sampled a few (but not all) of them and they are different only
because just how common lines are matched up, which is expected.
next prev parent reply other threads:[~2008-11-08 21:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 20:01 absurdly slow git-diff Abhijit Menon-Sen
2008-11-07 21:28 ` Mike Hommey
2008-11-07 21:37 ` Linus Torvalds
2008-11-07 23:04 ` Davide Libenzi
2008-11-07 23:18 ` Davide Libenzi
2008-11-07 23:42 ` Linus Torvalds
2008-11-07 23:48 ` Davide Libenzi
2008-11-07 23:57 ` Linus Torvalds
2008-11-08 4:57 ` Abhijit Menon-Sen
2008-11-08 21:02 ` Junio C Hamano [this message]
2008-11-08 5:30 ` Junio C Hamano
2008-11-08 16:27 ` Davide Libenzi
2008-11-08 0:14 ` Pierre Habouzit
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=7vr65maq2r.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=ams@toroid.org \
--cc=davidel@xmailserver.org \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
--cc=torvalds@linux-foundation.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