From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Thomas Rast <trast@inf.ethz.ch>, Luke Diamand <luke@diamand.org>,
Git List <git@vger.kernel.org>
Subject: Re: Tilde spec - befuzzled
Date: Wed, 29 Feb 2012 10:32:06 +0100 [thread overview]
Message-ID: <4F4DF096.9050905@op5.se> (raw)
In-Reply-To: <7vaa42zrw8.fsf@alter.siamese.dyndns.org>
On 02/28/2012 08:20 PM, Junio C Hamano wrote:
> Thomas Rast<trast@inf.ethz.ch> writes:
>
>>>> '<rev>{tilde}<n>', e.g. 'master{tilde}3'::
>>>> A suffix '{tilde}<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 parents.
>>>>
>>>> Hang on, *grand*-parents?
>>>> ...
>>
>> Perhaps we should reword it as "n-th first-parent ancestor"? Barring
>> confusion about the position of the dashes, that leaves little room for
>> error.
>
> I think we could either go "easier to read but not precise"
>
> ... that is the<n>th generation (grand-)parent of ...
>
(grand-)parent and ancestor are interchangeable while the parentheses
remain, although the former looks a bit clumsier in text.
> or "may sound scary but correct"
>
> the ancestor reached by walking the first-parent chain<n> times
>
> I am not sure which bucket "n-th first-parent ancestor" falls into.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2012-02-29 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 9:07 Tilde spec - befuzzled Luke Diamand
2012-02-28 9:50 ` Andreas Ericsson
2012-02-28 11:34 ` Thomas Rast
2012-02-28 19:20 ` Junio C Hamano
2012-02-29 1:18 ` Andrew Ardill
2012-02-29 7:34 ` Jeff King
2012-02-29 9:30 ` Andreas Ericsson
2012-02-29 9:32 ` Andreas Ericsson [this message]
2012-02-29 19:13 ` Re*: " Junio C Hamano
2012-03-02 9:25 ` Luke Diamand
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=4F4DF096.9050905@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luke@diamand.org \
--cc=trast@inf.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.