From: Julia Evans Date: Mon, 06 Oct 2025 21:46:46 GMT Subject: Re: [PATCH] doc: add a explanation of Git's data model Message-ID: <1241cb86-9adf-4c52-87fb-028406ccd8f0@app.fastmail.com> In-Reply-To: On Mon, Oct 6, 2025, at 5:44 PM, D. Ben Knoble wrote: > On Mon, Oct 6, 2025 at 3:37 PM Julia Evans wrote: >> >> Thanks for the review! >> >> >> 2. Don't mention that the full name of the branch `main` is >> >> technically `refs/heads/main`. This should likely change but I >> >> haven't worked out how to do it in a clear way yet. >> > >> > I think this is worth getting into. This is a pretty >> > user-facing concept. >> >> I think I'll see if I can figure out a way to mention this and at the >> same time remove most of the rest of the references to the `.git` >> directory when explaining references (which you talked about >> further down), including packed refs. > > A colleague will be explaining reflog for an audience tomorrow, and > decided to briefly explain refs, too—which tells me this is > much-needed. > > For refs themselves, perhaps "git for-each-ref" is a reasonable place > to start? Since it tells you the refs you have and how to spell them > explicitly regardless of how they are stored? Interesting, do you use git for-each-ref? What do you use it for? > -- > D. Ben Knoble