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, 08:52 UTC
Message-ID
<CAHGBnuOuMnAsP12dukPSP31ABRoUc=s7iZFnca9-K2hOcog9cQ@mail.gmail.com>
In-Reply-To
<CAPc5daXRpfSrvcae0W+YU-51prCoFGxz_hkhtp7FZ-K9_eeeBQ@mail.gmail.com>
On Tue, Apr 14, 2015 at 10:05 AM, Junio C Hamano <gitster@pobox.com> wrote:
> A dangling object is an unreachable object that cannot be
> made reachable by any way other than pointing at it
> directly with a ref.
Thanks a lot for the prompt explanation!
-- 
Sebastian Schuberth
Previous: Michael J GruberNext: Sebastian Schuberth
Message 8 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.