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

Re: git fsck messages - what to do about it?

From
Horst von Brand <vonbrand@inf.utfsm.cl>
Date
Sep 16, 2005, 19:37 UTC
Message-ID
<200509161937.j8GJbv62018950@inti.inf.utfsm.cl>
In-Reply-To
<wd@denx.de>
Wolfgang Denk <wd@denx.de> wrote:
Show 5 quoted lines
> When running git fsck I get some messages:
> 
> -> git-fsck-cache --unreachable $(cat .git/HEAD .git/refs/heads/*)
> unreachable commit 08cf4121ad704faa5ae7c7ae7b3dca4476ef2770
> unreachable tree 29a4c18afd958cc6cee938f0fe7fa59764418097
[...]
> I have to admit that I don't know what to do next...
> 
> a) I understand that these  messages  are  indications  of  problems,
>    right? What can I do to clean this up?

One of the nits I'd like to pick is that git-fsck does only check, not (like its filesystem counterparts) fix the problems it finds.

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
Next: Horst von Brand
Message 1 of 2 in “Re: git fsck messages - what to do about it?”
  1. Horst von BrandSep 16, 2005
  2. Horst von BrandOct 31, 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.