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

Re: Confused as to the correct syntax

From
Junio C Hamano <junkio@cox.net>
Date
Oct 5, 2005, 23:16 UTC
Message-ID
<7v7jcrh7wu.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200510052350.07217.alan@chandlerfamily.org.uk>
Alan Chandler <alan@chandlerfamily.org.uk> writes:
Show 8 quoted lines
> "A  suffix  ~<n>  to  a  revision parameter means the 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^ which is equivalent to 
> rev11^1."
>
> Why is rev~3 equivalent to rev^,  surely it is equivalent to rev^^^
>
> Why is rev~3 equivalent to rev11^1, should that not be rev^1^1^1
Sorry, for not knowing how to do that properly in Asciidoc ;-).
The source to the man page and HTML page reads like this:
* A suffix '~<n>' to a revision parameter means the 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^^^ which is equivalent to rev^1^1^1.
Previous: Alan ChandlerNext: Alan Chandler
Message 2 of 6 in “Confused as to the correct syntax”
  1. Alan ChandlerOct 5, 2005
  2. Junio C HamanoOct 5, 2005
  3. Alan ChandlerOct 5, 2005
  4. Junio C HamanoOct 5, 2005
  5. Fix usage of carets in git-rev-parse(1)Jonas Fonseca, Oct 5, 2005
  6. Junio C HamanoOct 6, 2005

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.