git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] git-rev-parse.txt: clarify meaning of rev~ and rev~0.

From
SOSergei Organov <osv@javad.com>
Date
Mar 14, 2008, 17:20 UTC
Message-ID
<87wso5mcs7.fsf@osv.gnss.ru>
Signed-off-by: Sergei Organov <osv@javad.com>
---
 Documentation/git-rev-parse.txt |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 6513c2e..0234f89 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -200,8 +200,9 @@ blobs contained in a commit.
   object that is the <n>th generation grand-parent of the named
   commit object, following only the first parent.  I.e. rev~3 is
   equivalent to rev{caret}{caret}{caret} which is equivalent to
-  rev{caret}1{caret}1{caret}1.  See below for a illustration of
-  the usage of this form.
+  rev{caret}1{caret}1{caret}1.  See below for an illustration of
+  the usage of this form.  'rev{tilde}' is equivalent to 'rev{tilde}0'
+  which in turn is equivalent to 'rev'.
 
 * A suffix '{caret}' followed by an object type name enclosed in
   brace pair (e.g. `v0.99.8{caret}\{commit\}`) means the object
-- 
1.5.4.4.551.g1658c
Next: Linus Torvalds
Message 1 of 4 in “git-rev-parse.txt: clarify meaning of rev~ and rev~0.”
  1. git-rev-parse.txt: clarify meaning of rev~ and rev~0.Sergei Organov, Mar 14, 2008
  2. Linus TorvaldsMar 14, 2008
  3. Sergei OrganovMar 14, 2008
  4. Junio C HamanoMar 14, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.