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

Re: Verifying the whole repository

From
David Symonds <dsymonds@gmail.com>
Date
Oct 23, 2008, 14:05 UTC
Message-ID
<ee77f5c20810230705l20339a1dj87b855bf3321f796@mail.gmail.com>
In-Reply-To
<b2cdc9f30810230659n15f44f64l571a0df3dbe104d9@mail.gmail.com>
On Thu, Oct 23, 2008 at 6:59 AM, Alex Bennee <kernel-hacker@bennee.com> wrote:
Show 7 quoted lines
> As git is fundamentally hash based it's a lot easier to determine the
> health of the repository but I wonder if it's possible for silent
> corruption to creep in which won't be noticed until you try and
> checkout a historical commit of the tree. I notice there is a
> git-verify-pack command that checks the pack files are OK. Do any of
> the other commands implicitly ensure all objects in the repo are
> correct and valid? git-gc?
Try:  git fsck --full --strict
Dave.
Previous: Alex BenneeNext: Alex Bennee
Message 2 of 4 in “Verifying the whole repository”
  1. Alex BenneeOct 23, 2008
  2. David SymondsOct 23, 2008
  3. Alex BenneeOct 23, 2008
  4. Shawn O. PearceOct 23, 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.