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

Re: [PATCH] don't mention index refreshing side effect in git-status docs

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 9, 2007, 08:33 UTC
Message-ID
<7vhciss1ww.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20071209082133.GA2257@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> If there is some desire to document the side effect, I think we should
> at least remove the mention of speeding up git-diff (which is just wrong
> now).

Why is it "just wrong"? Having to squelch the false hits and to run auto-refresh are both unnecessary overhead if your index is fresh.

Previous: Jeff KingNext: Jeff King
Message 2 of 5 in “don't mention index refreshing side effect in git-status docs”
  1. don't mention index refreshing side effect in git-status docsJeff King, Dec 9, 2007
  2. Junio C HamanoDec 9, 2007
  3. Jeff KingDec 9, 2007
  4. Jonathan del StrotherDec 9, 2007
  5. Junio C HamanoDec 9, 2007

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.