Browse Source

Documentation: clarify "working tree" definition

It is not necessarily obvious to a git novice what it means for a
filesystem tree to be equal to the HEAD.  Spell it out.

Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Jonathan Nieder 16 years ago committed by Junio C Hamano
parent
commit
580cbb58a2
  1. 6
      Documentation/glossary-content.txt

6
Documentation/glossary-content.txt

@ -456,6 +456,6 @@ This commit is referred to as a "merge commit", or sometimes just a
of 'A' is 'origin/B' sometimes we say "'A' is tracking 'origin/B'". of 'A' is 'origin/B' sometimes we say "'A' is tracking 'origin/B'".


[[def_working_tree]]working tree:: [[def_working_tree]]working tree::
The tree of actual checked out files. The working tree is The tree of actual checked out files. The working tree normally
normally equal to the <<def_HEAD,HEAD>> plus any local changes contains the contents of the <<def_HEAD,HEAD>> commit's tree,
that you have made but not yet committed. plus any local changes that you have made but not yet committed.

Loading…
Cancel
Save