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

git fsck messages - what to do about it?

From
WDWolfgang Denk <wd@denx.de>
Date
Sep 16, 2005, 10:11 UTC
Message-ID
<20050916101138.99906352682@atlas.denx.de>
When running git fsck I get some messages:

-> git-fsck-cache --unreachable $(cat .git/HEAD .git/refs/heads/*) unreachable commit 08cf4121ad704faa5ae7c7ae7b3dca4476ef2770 unreachable tree 29a4c18afd958cc6cee938f0fe7fa59764418097 unreachable tree 3b722a7278e02b272ddc8aefbc7be22703d8a94f unreachable tree 4ebc50d240d99b4236952d13d5044691f9078e3c unreachable tree 63af5944e130b449338cc907ee77c51f4a69e339 unreachable tree 79c9a6bb02a80df15c7d829bdac0901f88c5e301 unreachable blob 85dcf4b5c4c0f6833cd63fa1d0fd29ef250162af unreachable commit c1b779fbce762c970e3ace4332bb6ddc0de65e61 unreachable blob d70d1d44f12db7b2a3976c2a5313c90568a62c25 unreachable commit e1bcd2a5d53bceef2679737474487e32d87e7f2c

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?
b) Is there any way to find out what I did wrong in the first place?

In case it matters: the tree in question is available at {rsync,http}://source.denx.net/git/u-boot.git

Thanks in advance,
Best regards,
Wolfgang Denk
-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"This isn't brain surgery; it's just television."   - David Letterman
Next: Catalin Marinas
Message 1 of 9 in “git fsck messages - what to do about it?”
  1. Wolfgang DenkSep 16, 2005
  2. Catalin MarinasSep 16, 2005
  3. Wolfgang DenkSep 16, 2005
  4. Junio C HamanoSep 16, 2005
  5. Petr BaudisSep 16, 2005
  6. Linus TorvaldsSep 16, 2005
  7. Linus TorvaldsSep 16, 2005
  8. Linus TorvaldsSep 18, 2005
  9. Junio C HamanoSep 18, 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.