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

git fsck: unreachable vs. dangling

From
Sebastian Schuberth <sschuberth@gmail.com>
Date
Apr 14, 2015, 07:16 UTC
Message-ID
<CAHGBnuOYLpkeUop9vNH3+WSKqrM3NCSqvu-NZnPnk3gEkAr6eg@mail.gmail.com>
Hi,

reading through the fsck docs [1] I'm having a hard time understanding what the difference between "unreachable" and "dangling" objects are.

By example, suppose I have a commit A that is the tip of exactly one branch (and no tag or other ref points to A). If I delete that branch, is A now dangling, or unreachable, or both?

[1] http://git-scm.com/docs/git-fsck.html
-- 
Sebastian Schuberth
Next: Junio C Hamano
Message 1 of 9 in “git fsck: unreachable vs. dangling”
  1. Sebastian SchuberthApr 14, 2015
  2. Junio C HamanoApr 14, 2015
  3. Michael J GruberApr 14, 2015
  4. Sebastian SchuberthApr 14, 2015
  5. Junio C HamanoApr 14, 2015
  6. Sebastian SchuberthApr 14, 2015
  7. Michael J GruberApr 14, 2015
  8. Sebastian SchuberthApr 14, 2015
  9. Sebastian SchuberthApr 14, 2015

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.