Re: [PATCH 3/3] Add a few more words to the glossary.
- From
Junio C Hamano <junkio@cox.net>
- Date
- May 4, 2006, 05:58 UTC
- Message-ID
- <7vu0868h7a.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <E1FbVJi-0004UJ-59@jdl.com>
Jon Loeliger <jdl@jdl.com> writes:
Show 8 quoted lines
> ref:: > - A 40-byte hex representation of a SHA1 pointing to a particular > - object. These may be stored in `$GIT_DIR/refs/`. > + A 40-byte hex representation of a SHA1 or a name that denotes > + a particular object. These may be stored in `$GIT_DIR/refs/`. > > +symbolic ref:: > + See "ref".
Uum. Not very clear. Do we use that word that often?
I think I used that term to differenciate between HEAD symlink pointing at refs/heads/master and HEAD being a regular file that stores a line "ref: refs/heads/master\n"; the latter is the modern style "textual symref", so in that context it is not about 40-byte hex at all. And at that level it is really a jargon to talk about one small implementation detail of HEAD, so I am not sure it deserves to be in the glossary.
> tracking branch:: > - A regular git branch that is used to follow changes from > + A regular git branch that is used to follow changes frompointing > another repository. A tracking branch should not contain
I think this is a typo?