Re: [PATCH] doc: add a explanation of Git's data model
- From
D. Ben Knoble <ben.knoble@gmail.com>
- Date
- Oct 6, 2025, 21:44 UTC
- Message-ID
- <CALnO6CA29HA_FOQAJp_bkskKF-6Vy0_SKVL_OyJASByvKEZTqQ@mail.gmail.com>
- In-Reply-To
- <51e0a55c-1f1d-4cae-9459-8c2b9220e52d@app.fastmail.com>
On Mon, Oct 6, 2025 at 3:37 PM Julia Evans <julia@jvns.ca> wrote:
Show 14 quoted lines
> > 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?
-- D. Ben Knoble