git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Alan Chandler <alan@chandlerfamily.org.uk>
Cc: git@vger.kernel.org
Subject: Re: Confused as to the correct syntax
Date: Wed, 05 Oct 2005 16:16:01 -0700	[thread overview]
Message-ID: <7v7jcrh7wu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200510052350.07217.alan@chandlerfamily.org.uk> (Alan Chandler's message of "Wed, 5 Oct 2005 23:50:07 +0100")

Alan Chandler <alan@chandlerfamily.org.uk> writes:

> "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.

  reply	other threads:[~2005-10-05 23:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 22:50 Confused as to the correct syntax Alan Chandler
2005-10-05 23:16 ` Junio C Hamano [this message]
2005-10-05 23:33   ` Alan Chandler
2005-10-05 23:54     ` Junio C Hamano
2005-10-05 23:42   ` [PATCH] Fix usage of carets in git-rev-parse(1) Jonas Fonseca
2005-10-06  0:06     ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7v7jcrh7wu.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=alan@chandlerfamily.org.uk \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).