diff options
| author |  Junio C Hamano <gitster@pobox.com> | 2022-02-09 18:19:07 -0800 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2022-02-09 18:34:41 -0800 |
| commit | 2df5387ed04159b188de65dff9654d4aae1062d2 (patch) | |
| tree | 59e90c642c015394d37d2436bb7440ca3f0a2100 /t/t9157-git-svn-fetch-merge.sh | |
| parent | Git 2.35.1 (diff) | |
| download | tgif-2df5387ed04159b188de65dff9654d4aae1062d2.tar.xz | |
glossary: describe "worktree"
We have description on "per worktree ref", but "worktree" is not
described in the glossary. We do have "working tree", though.
Casually put, a "working tree" is what your editor and compiler
interacts with. "worktree" is a mechanism to allow one or more
"working tree"s to be attached to a repository and used to check out
different commits and branches independently, which includes not
just a "working tree" but also repository metadata like HEAD, the
index to support simultaneous use of them. Historically, we used
these terms interchangeably but we have been trying to use "working
tree" when we mean it, instead of "worktree".
Most of the existing references to "working tree" in the glossary do
refer primarily to the working tree portion, except for one that
said refs like HEAD and refs/bisect/* are per "working tree", but it
is more precise to say they are per "worktree".
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9157-git-svn-fetch-merge.sh')
0 files changed, 0 insertions, 0 deletions