From: Petr Baudis <pasky@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Russell King <rmk@arm.linux.org.uk>, git@vger.kernel.org
Subject: Re: Is cogito really this inefficient
Date: Wed, 20 Jul 2005 01:54:52 +0200 [thread overview]
Message-ID: <20050719235452.GE2255@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0507140813150.19183@g5.osdl.org>
Dear diary, on Thu, Jul 14, 2005 at 05:26:07PM CEST, I got a letter
where Linus Torvalds <torvalds@osdl.org> told me that...
> It's quite possible that some path in cg-update ends up not updating the
> index properly. For example, I notice that the "fast-forward" uses
> "git-checkout-cache -f -a", which can do so (lack of "-u" fila), but then
> it does do a "git-update-cache --refresh" later, so that doesn't seem to
> be it either.
Just a side note for casual readers, Cogito could use a cleanup here -
from large part it ignores things like git-checkout-cache -u simply
because there was no such option at the time that part of Cogito was
written. I myself am not even too familiar about those gazillions of
funny new options, and as long as it works, I prefer not to touch that
code, but if someone is bored and wants to get familiar with core git
usage as well as Cogito internals...
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
prev parent reply other threads:[~2005-07-19 23:55 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
2005-07-15 9:48 ` Russell King
2005-07-14 15:26 ` Linus Torvalds
2005-07-19 23:54 ` Petr Baudis [this message]
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=20050719235452.GE2255@pasky.ji.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--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).