git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.30.0-rc2
Date: Wed, 23 Dec 2020 22:36:07 -0800	[thread overview]
Message-ID: <xmqq7dp74so8.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqqblej4t1a.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Wed, 23 Dec 2020 22:28:17 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> Christian Couder <christian.couder@gmail.com> writes:
>
>> Most of the suggestions below are found by GMail.
>>
>> On Thu, Dec 24, 2020 at 12:08 AM Junio C Hamano <gitster@pobox.com> wrote:
>>>
>>> A release candidate Git v2.30.0-rc2 is now available for testing
>>> at the usual places.  It is comprised of 19 non-merge commits since
>>
>> Maybe: s/is comprised of/comprises/
>
> Funny.  
>
> I do recall somebody else (perhaps Peff but I may be misremembering)
> helped me grammofixing the use of verb "comprise" in the sentence
> when I started listing the names of commit authors back in v2.3.3 or
> v2.4.0 era.  Perhaps I failed to follow the advice given?  I dunno.

Ah, just to avoid duplicated archive digging effort, it indeed was
in https://lore.kernel.org/git/20150312223131.GA24492@peff.net/
where Peff said

    > ... usual places.  It comprises of 41 non-merge commits since
    > v2.3.1, contributed by 19 people, 5 of which are new faces.

    It's not generally considered correct to use "of" with the active
    tense of "comprise". So either:

      It comprises 41 non-merge commits...

    or:

      It is comprised of 41 non-merge commits...

    is fine.  The latter is much more common, at least in American
    English, though I imagine it gives some prescriptivists headaches.

and the Meta/Announce script has stuck to the latter form since
then.

Thanks anyway.

  reply	other threads:[~2020-12-24  6:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23 23:05 [ANNOUNCE] Git v2.30.0-rc2 Junio C Hamano
2020-12-24  0:22 ` Todd Zullinger
2020-12-24  0:48   ` Junio C Hamano
2020-12-24  6:13 ` Christian Couder
2020-12-24  6:28   ` Junio C Hamano
2020-12-24  6:36     ` Junio C Hamano [this message]
2020-12-24 14:49       ` Randall S. Becker
2020-12-24 15:16         ` Felipe Contreras

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=xmqq7dp74so8.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --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).