All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: marcnarc@xiplink.com
Cc: Thomas Adam <thomas@xteddy.org>,
	Eric Sunshine <sunshine@sunshineco.com>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	Git List <git@vger.kernel.org>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	Jeff King <peff@peff.net>, Duy Nguyen <pclouds@gmail.com>
Subject: Re: "lets" vs. "let's"
Date: Wed, 01 May 2013 10:18:50 -0700	[thread overview]
Message-ID: <7v61z28vph.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5181257C.2050108@xiplink.com> (Marc Branchaud's message of "Wed, 01 May 2013 10:23:56 -0400")

Marc Branchaud <mbranchaud@xiplink.com> writes:

> On 13-05-01 06:31 AM, Thomas Adam wrote:
>> On 1 May 2013 11:12, Eric Sunshine <sunshine@sunshineco.com> wrote:
>>> On Wed, May 1, 2013 at 5:51 AM, Felipe Contreras
>>> <felipe.contreras@gmail.com> wrote:
>>>> So HEAD@{0}~0^0 is too much to type, but we can remove '^0', and we can
>>>> remove '~0', and we can remove 'HEAD', which leaves us with @{0}, but we
>>>> can't remove '{0}'?
>>>>
>>>> This patch allows '@' to be the same as 'HEAD'.
>>>>
>>>> So now we can use 'git show @~1', and all that goody goodness.
>>>>
>>>> Until now '@' was a valid name, but it conflicts with this idea, so lets
>>>
>>> s/lets/let's/  (contraction of "let us")
>> 
>> Ah, the contraction versus the first person singular.  In this case
>> where the context is concluding in decision, rather than making a
>> statement ("Let's go to the shops", for example) then "lets" is the
>> correct word to use here.
>
> You've lost me.  I think Eric is right.  If "lets" is a verb in this
> sentence, what is its subject?
>
> Besides, of which verb & tense is "lets" the first person singular?  Never
> have I "lets" anything in my life...  :)

I'll queue with:

	... '@' was a valid name, but it conflicts with this idea,
	so make it invalid.

That is, just use the imperative mood to give an order to the
codebase to "make it so", which is a common style of log messages in
this project.

  reply	other threads:[~2013-05-01 17:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01  9:51 [PATCH v3] Add new @ shortcut for HEAD Felipe Contreras
2013-05-01 10:12 ` Eric Sunshine
2013-05-01 10:31   ` Thomas Adam
2013-05-01 14:23     ` "lets" vs. "let's" (was: Re: [PATCH v3] Add new @ shortcut for HEAD) Marc Branchaud
2013-05-01 17:18       ` Junio C Hamano [this message]
2013-05-01 17:53 ` [PATCH v3] Add new @ shortcut for HEAD Junio C Hamano
2013-05-01 18:33   ` Felipe Contreras
2013-05-01 22:08     ` Junio C Hamano
2013-05-01 22:35       ` Felipe Contreras
2013-05-01 22:59         ` Junio C Hamano
2013-05-01 23:14           ` Felipe Contreras
2013-05-02  2:33             ` Felipe Contreras
2013-05-06 14:48               ` Junio C Hamano
2013-05-01 22:56       ` 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=7v61z28vph.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=artagnon@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=marcnarc@xiplink.com \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=sunshine@sunshineco.com \
    --cc=thomas@xteddy.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 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.