From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Is cogito really this inefficient
Date: Thu, 14 Jul 2005 19:10:28 -0700 [thread overview]
Message-ID: <7vll48250r.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.58.0507141725280.19183@g5.osdl.org
Linus Torvalds <torvalds@osdl.org> writes:
> On Thu, 14 Jul 2005, Linus Torvalds wrote:
>>
>> I'll look into making diff-cache be more efficient. I normally don't use
>> it myself, so I didn't bother (I use git-diff-files, which is way more
>> efficient, but doesn't show the difference against the _tree_, it shows
>> the difference against the index. Since cogito tries to hide the index
>> from you, cogito can't very well use that).
>
> Ok, done.
Wonderful.
> Junio - I think this makes gitcore-pathspec pretty pointless, but I didn't
> actually remove it. I guess "git-diff-helper" still uses it.
And probably it shouldn't; diff-helper should be raw-to-patch
converter, nothing more.
Usually I'd volunteer to clean up the remaining mess (which was
originally my mess anyway) myself, but since I'd already asked
smurf to help cleaning up the diff option parsing, and recently
I've suddenly got quite busy in the day job, so ...
next prev parent reply other threads:[~2005-07-15 2:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 12:50 Is cogito really this inefficient Russell King
2005-07-13 16:51 ` Matthias Urlichs
2005-07-14 7:38 ` Russell King
2005-07-13 20:28 ` Linus Torvalds
2005-07-14 7:37 ` Russell King
2005-07-14 9:08 ` Catalin Marinas
2005-07-14 9:59 ` Russell King
2005-07-14 15:51 ` Linus Torvalds
2005-07-15 0:29 ` Linus Torvalds
2005-07-15 2:10 ` Junio C Hamano [this message]
2005-07-15 9:48 ` Russell King
2005-07-14 15:26 ` Linus Torvalds
2005-07-19 23:54 ` Petr Baudis
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=7vll48250r.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).