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

Re: Should git-prune-script warn about dircache?

From
Linus Torvalds <torvalds@osdl.org>
Date
May 1, 2005, 16:18 UTC
Message-ID
<Pine.LNX.4.58.0505010916510.2296@ppc970.osdl.org>
In-Reply-To
<7vwtqjxlrv.fsf@assigned-by-dhcp.cox.net>
On Sun, 1 May 2005, Junio C Hamano wrote:
> 
> Maybe a big warning in red ugly bold blinking typeface somewhere
> in the doc?

How about making git-prune-script first run "git-update-cache --refresh", and checking the return value of it (this, of course, assumes that git-update-cache --refresh would return non-zero if it can't refresh a file, which is currently not true, but should be easily fixable).

		Linus
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 6 in “Should git-prune-script warn about dircache?”
  1. Junio C HamanoMay 1, 2005
  2. Linus TorvaldsMay 1, 2005
  3. Junio C HamanoMay 1, 2005
  4. Junio C HamanoMay 1, 2005
  5. Make git-prune-script a bit more careful.Junio C Hamano, May 1, 2005
  6. Make git-update-cache --refresh fail if update/merge needed.Junio C Hamano, May 1, 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.