From: Jonathan Nieder Date: Sun, 21 Apr 2013 08:17:05 GMT Subject: [PATCH/RFC] glossary: a revision is just a commit Message-ID: <20130421081705.GG10429@elie.Belkin> In-Reply-To: The current definition of 'revision' sounds like it is saying that a revision is a tree object. In reality it is just a commit. This should be especially useful for people used to other revision control systems trying to see how familiar concepts translate into git terms. Reported-by: Ramkumar Ramachandra Signed-off-by: Jonathan Nieder --- Junio C Hamano wrote: > On Apr 21, 2013 12:41 AM, "Jonathan Nieder" wrote: >>> revision:: A particular state of files and directories which was >>> stored in the object database. It is referenced by a commit object. >> >> So a revision is a tree? [...] > That's a historical misnomer. Some places in the documentation use revision > as if the word were interchangeable with object name, and HEAD:path listed > in specifying revision section is a prime example of it. What the section > lists is historically called extended SHA-1 expression, essentially what > get_sha1() can grok down to a single object name (as opposed to a slice of > history, which is a revision range). Thanks. Documentation/glossary-content.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt index eb7ba84f..521fceeb 100644 --- a/Documentation/glossary-content.txt +++ b/Documentation/glossary-content.txt @@ -430,9 +430,7 @@ should not be combined with other pathspec. <> left behind. [[def_revision]]revision:: - A particular state of files and directories which was stored in the - <>. It is referenced by a - <>. + Synonym for <> (the noun). [[def_rewind]]rewind:: To throw away part of the development, i.e. to assign the -- 1.8.2.1