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

Re: [RFC/PATCH] fsck: do not canonicalize modes in trees we are checking

From
Jeff King <peff@peff.net>
Date
Oct 14, 2014, 08:21 UTC
Message-ID
<20141014082120.GA16686@peff.net>
In-Reply-To
<543B02A7.9040807@optusnet.com.au>
On Mon, Oct 13, 2014 at 09:37:27AM +1100, Ben Aveling wrote:
> A question about fsck - is there a reason it doesn't have an option to
> delete bad objects?

If the objects are reachable, then deleting them would create other big problems (i.e., we would be breaking the object graph!).

If they are not, then it is probably safest for them to go away via the normal means (repack/prune via "git gc"). Deleting via fsck would mean replicating the reachability and deletion code found elsewhere.

-Peff
Previous: Ben AvelingNext: Jeff King
Message 5 of 8 in “fsck: do not canonicalize modes in trees we are checking”
  1. fsck: do not canonicalize modes in trees we are checkingJeff King, Sep 23, 2014
  2. Edward ThomsonSep 23, 2014
  3. Jeff KingSep 23, 2014
  4. Ben AvelingOct 12, 2014
  5. Jeff KingOct 14, 2014
  6. Jeff KingOct 16, 2014
  7. Ben AvelingOct 19, 2014
  8. Jeff KingOct 20, 2014

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.