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

[RFC] Fsck while fetching

From
MKMartin Koegler <mkoegler@auto.tuwien.ac.at>
Date
Mar 4, 2008, 07:55 UTC
Message-ID
<20080304075545.GA31793@auto.tuwien.ac.at>

As the infrastructure for checking the objects and their connectivity while pushing is in place, it is easy to do the same while fetching on non shallow repositories.

On shallow repositories this is currently only possible, if the list of shallow commits does not change (eg. no depth option).

The neccessary changes are:
* Read a config option in fetch-pack to disable it (default: true)
* Add in fetch-pack --strict to the command lines of index-pack and 
  unpack-objects, if the config option is true and args.depth is 0.
This leads to the question:
* How should the config option be named? fetch.fsckObjects? Should
  receive.fsckObjects be reused? Should receive.fsckObjects be renamed
  to a new name, which is used in both cases?
On additional question:
* fsck has a strict option, which looks for files with 0664 mode. How
  should such files be handled with the checking while pushing/fetching:
  ignored, rejected or config option for the behaviour?
mfg Martin Kögler
Message 1 of 1 in “[RFC] Fsck while fetching”
  1. Martin KoeglerMar 4, 2008

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.