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

Re: git fsck: unreachable vs. dangling

From
Sebastian Schuberth <sschuberth@gmail.com>
Date
Apr 14, 2015, 09:28 UTC
Message-ID
<CAHGBnuNA7fVKJRA-oMbnL5J+zoe7F6sy0rU_0PvAX52x0ofXdQ@mail.gmail.com>
In-Reply-To
<xmqq1tjn3vzs.fsf@gitster.dls.corp.google.com>
On Tue, Apr 14, 2015 at 11:22 AM, Junio C Hamano <gitster@pobox.com> wrote:
> I just visualize commits to be ping-pong balls with strings between
> them, and then grab the root of the graph and lift the whole thing
> up, while tips of the branches and tags are anchored.  Commit A will
> be dangling in the wind if you shake the whole thing.

I used to have exactly the same visualization in mind, but got confused in between, unsure whether my understanding was correct. As it turns out it is, and when sticking to that visualization everything seems to be consistent in the fsck docs. They could still benefit some more clarification I guess. I'll see if I can come up with something.

Thanks again.
-- 
Sebastian Schuberth
Previous: Junio C HamanoNext: Michael J Gruber
Message 6 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.