Re: [PATCH 2/2] Document rev^! and rev^@ as revision specifiers

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 6, 2012, 07:21 UTC
Message-ID: <7vtxxlnyn1.fsf@alter.siamese.dyndns.org>
In-Reply-To: <1341532890-13829-2-git-send-email-max@quendi.de>

Max Horn <max@quendi.de> writes:

Show 6 quoted lines

> +'<rev>{caret}@', e.g. 'HEAD{caret}@'::
> +  A suffix '{caret}' followed by an at sign
> +  means all parents of '<rev>'.
> +  This is somewhat different from the other specifiers in this
> +  section in that it may refer to multiple commits at once.
> +  See also the next section on SPECIFYING RANGES.

Looks good.

> +'<rev>{caret}!', e.g. 'HEAD{caret}!'::
> +  A suffix '{caret}' followed by an exclamation mark
> +  means commit '<rev>' but forces all of its parents to be excluded. For
> +  commands that deal with a single revision, this is the same as '<rev>".

Is this sentence correct? "git commit -C 'HEAD^!'" might be a command that expects a single revision, but I do not think it is the same as "git commit -C HEAD".

> +  Hence it is primarily used with commands expecting commit ranges.

That is correct.