git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Is cogito really this inefficient

From
Linus Torvalds <torvalds@osdl.org>
Date
Jul 13, 2005, 20:28 UTC
Message-ID
<Pine.LNX.4.58.0507131325170.17536@g5.osdl.org>
In-Reply-To
<20050713135052.C6791@flint.arm.linux.org.uk>
On Wed, 13 Jul 2005, Russell King wrote:
>
> This says it all.  1min 22secs to generate a patch from a locally
> modified but uncommitted file.
No, there's something else going on.

Most likely that something forced a total index file re-validation, and the time you see is every single checked out file having its SHA1 re-computed.

Was this a recently cloned tree, or what was the last operation you did on that tree before that command? Something must have invalidated the index.

			Linus
Previous: Russell KingNext: Russell King
Message 4 of 13 in “Is cogito really this inefficient”
  1. Russell KingJul 13, 2005
  2. Matthias UrlichsJul 13, 2005
  3. Russell KingJul 14, 2005
  4. Linus TorvaldsJul 13, 2005
  5. Russell KingJul 14, 2005
  6. Catalin MarinasJul 14, 2005
  7. Russell KingJul 14, 2005
  8. Linus TorvaldsJul 14, 2005
  9. Linus TorvaldsJul 15, 2005
  10. Junio C HamanoJul 15, 2005
  11. Russell KingJul 15, 2005
  12. Linus TorvaldsJul 14, 2005
  13. Petr BaudisJul 19, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.