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, 18:15 UTC
Message-ID
<7vhcirpwdk.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<57518fd10712090816pa43cf97mbc1b8f5fbe81c66f@mail.gmail.com>
"Jonathan del Strother" <maillist@steelskies.com> writes:
> ... the GIT-VERSION-GEN
> script occasionally gives me spurious 'dirty' results (eg when a file
> timestamp changes despite the content having changed).

Good eyes. Either refreshing before diff-index or using the "git diff" Porcelain would be more appropriate.

Previous: Jonathan del Strother
Message 5 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.