glossary: a revision is just a commit
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 <artagnon@gmail.com> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonathan Nieder committed
Apr 21, 2013 at 01:17 UTC
dfb44106cdad20d4cf251b31cff154525a291326
1 file changed
+1
-3
Documentation/glossary-content.txt
+1
-3
@@ -430,9 +430,7 @@ should not be combined with other pathspec.
430
<<def_merge,merge>> left behind.
431
432
[[def_revision]]revision::
433
- A particular state of files and directories which was stored in the
434
- <<def_object_database,object database>>. It is referenced by a
435
- <<def_commit_object,commit object>>.
433
+ Synonym for <<def_commit,commit>> (the noun).
434
435
[[def_rewind]]rewind::
436
To throw away part of the development, i.e. to assign the