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
Reported-by: Ramkumar Ramachandra <artag...@gmail.com>
Signed-off-by: Jonathan Nieder <jrnie...@gmail.com>
Junio C Hamano wrote:
> On Apr 21, 2013 12:41 AM, "Jonathan Nieder" <jrnie...@gmail.com> 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).
Documentation/glossary-content.txt | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/Documentation/glossary-content.txt
index eb7ba84f..521fceeb 100644
@@ -430,9 +430,7 @@ should not be combined with other pathspec.
<<def_merge,merge>> left behind.
- A particular state of files and directories which was stored in the
- <<def_object_database,object database>>. It is referenced by a
- <<def_commit_object,commit object>>.
+ Synonym for <<def_commit,commit>> (the noun).
To throw away part of the development, i.e. to assign the
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html