From: Russell King <rmk@arm.linux.org.uk>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: git@vger.kernel.org
Subject: Re: Is cogito really this inefficient
Date: Thu, 14 Jul 2005 08:38:31 +0100 [thread overview]
Message-ID: <20050714083831.B26322@flint.arm.linux.org.uk> (raw)
In-Reply-To: <pan.2005.07.13.16.51.28.520681@smurf.noris.de>; from smurf@smurf.noris.de on Wed, Jul 13, 2005 at 06:51:30PM +0200
On Wed, Jul 13, 2005 at 06:51:30PM +0200, Matthias Urlichs wrote:
> Hi, Russell King wrote:
>
> > This says it all. 1min 22secs to generate a patch from a locally
> > modified but uncommitted file.
>
> I only get that when the index is out-of-date WRT the file modification
> dates, so cg-diff has to examine every file.
>
> The good news is that the index is being updated as it finds that the
> files are in sync, so expect this to be significantly faster the next time
> around.
It isn't. First time it was 1min11, second time _immediately_ after
it was 1min22. See my reply to Linus.
Oddly, show-diff seemed to be a lot more efficient in previous git
revisions.
--
Russell King
next prev parent reply other threads:[~2005-07-14 7:39 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 [this message]
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
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=20050714083831.B26322@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.