Re: [PATCH] glossary: describe "worktree"

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 10, 2022, 19:17 UTC
Message-ID: <xmqq7da2ttt7.fsf@gitster.g>
In-Reply-To: <CAFQ2z_Pvje9LM0iyiP87S-L754zepEE_9k=_4Oa0w1Lo_pb=TQ@mail.gmail.com>

Han-Wen Nienhuys <hanwen@google.com> writes:

Show 10 quoted lines

>> > Is this glossary the official definition of what things are? If so,
>> > the source code should refer to there. If not -except for confusion-
>> > how bad is it if the info in the glossary is inaccurate?
>>
>> Developer and end-user confusion ensues.
>
> that's why I said: "except for confusion" :-)
>
> I'm asking to understand if there is anything stopping us from
> changing the glossary to match the current code.

I do not think so. It will give us a chance to rethink what we have in the code, too. It is possible that we may end up concluding that it is better to leave a "pseudoref" always as a file inside $GIT_DIR regardless of what ref backend is in use, for example.