From: Patrick Steinhardt <ps@pks.im>
Date: Mon, 03 Nov 2025 07:40:28 GMT
Subject: Re: [PATCH v5] doc: add an explanation of Git's data model
Message-ID: <aQhcbHJjiI5GtV6Y@pks.im>
In-Reply-To: <xmqqtszf2kro.fsf@gitster.g>

On Fri, Oct 31, 2025 at 07:44:43AM -0700, Junio C Hamano wrote:
> "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
[snip]
> > +[[commit]]
> > +commit::
> > +    A commit contains these required fields
> > +    (though there are other optional fields):
> > ++
> > +1. The full directory structure of all the files in that version of the
> > +   repository and each file's contents, stored as the *<<tree,tree>>* ID
> > +   of the commit's base directory.
> 
> "base directory" is a new term; I think we most often use
> "top-level" directory (in various spellings).
> 
> $ git grep -e 'base directory' -e 'level directory' Documentation/

We'd refer to the top-level directory when talking about the worktree.
But what's referenced here is not referring to the worktree, but to the
commit's tree. And here I think we rather consistently use "root tree",
don't we? Our docs already mention "root tree" in several contexts.

Patrick