From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Jason Merrill <jason@redhat.com>, Alexander Monakov <amonakov@ispras.ru>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: [PATCH, v3] wwwdocs: e-mail subject lines for contributions
Date: Mon, 03 Feb 2020 15:15:00 -0000 [thread overview]
Message-ID: <8ae46cc6-d791-f84a-3230-27bed59f5844@arm.com> (raw)
In-Reply-To: <b187b673-f8cb-357e-f6fd-77e7bf358904@arm.com>
On 03/02/2020 15:13, Richard Earnshaw (lists) wrote:
> On 03/02/2020 14:10, Jason Merrill wrote:
>> On Mon, Feb 3, 2020 at 7:57 AM Alexander Monakov <amonakov@ispras.ru>
>> wrote:
>>
>>> On Mon, 3 Feb 2020, Richard Earnshaw (lists) wrote:
>>>
>>>> Upper case is what glibc has, though it appears that it's a rule
>>>> that is
>>> not
>>>> strictly followed. If we change it, then it becomes another friction
>>> point
>>>> between developer groups. Personally, I'd leave it as is, then turn a
>>> blind
>>>> eye to such minor non-conformance.
>>>
>>> In that case can we simply say that both 'committed' and 'COMMITTED' are
>>> okay,
>>> if we know glibc doesn't follow that rule and anticipate we will not
>>> follow
>>> it either?
>>>
>>
>> And perhaps something shorter? "committed" is a long word. [PUSHED]?
>>
>> Jason
>>
>
> "Committed" is the accepted term in glibc. If we insist on something
> different, then that becomes a friction point.
>
"COMMITTED", not "Committed".
> On the other hand, I really don't care personally as long as the meaning
> is clear. I'd be happy with the super-set of all of these, since it
> only appears in email messages, not the final commit.
>
> R.
next prev parent reply other threads:[~2020-02-03 15:15 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c3928f40-2d71-fb5b-f2e0-3878ac88a2b7@arm.com>
[not found] ` <alpine.LSU.2.21.2001191425160.739@anthias.pfeifer.com>
[not found] ` <353faf3e-bf43-eb4d-542d-45a53dce77b2@arm.com>
2020-01-21 15:40 ` [PATCH, v2] " Richard Earnshaw (lists)
2020-01-21 16:03 ` Jakub Jelinek
2020-01-21 16:14 ` Richard Earnshaw (lists)
2020-01-21 16:38 ` Jakub Jelinek
2020-01-21 16:43 ` Richard Earnshaw (lists)
2020-01-21 19:27 ` Jason Merrill
2020-01-22 3:46 ` Richard Earnshaw (lists)
2020-01-22 10:00 ` Jakub Jelinek
2020-01-22 13:50 ` Richard Earnshaw (lists)
2020-01-22 13:54 ` Jakub Jelinek
2020-01-22 17:41 ` Richard Sandiford
2020-01-22 17:45 ` Marek Polacek
2020-01-22 17:50 ` Richard Earnshaw (lists)
2020-01-22 9:07 ` Segher Boessenkool
2020-01-22 16:05 ` Richard Earnshaw (lists)
2020-01-22 16:37 ` Segher Boessenkool
2020-01-22 18:49 ` [PATCH, v3] " Richard Earnshaw (lists)
2020-02-03 11:41 ` Richard Earnshaw (lists)
2020-02-03 11:54 ` Alexander Monakov
2020-02-03 11:59 ` Richard Earnshaw (lists)
2020-02-03 12:51 ` Alexander Monakov
2020-02-03 14:11 ` Jason Merrill
2020-02-03 15:13 ` Richard Earnshaw (lists)
2020-02-03 15:15 ` Richard Earnshaw (lists) [this message]
2020-02-03 13:54 ` Segher Boessenkool
2020-02-03 14:00 ` Richard Earnshaw (lists)
2020-02-03 14:13 ` Jonathan Wakely
2020-02-03 15:05 ` Richard Earnshaw (lists)
2020-02-03 16:12 ` Andrew Clayton
2020-02-03 17:17 ` Segher Boessenkool
2020-02-03 17:19 ` Segher Boessenkool
2020-02-03 17:31 ` Michael Matz
2020-02-03 17:36 ` Richard Earnshaw (lists)
2020-02-03 17:49 ` Michael Matz
2020-02-03 17:54 ` Jakub Jelinek
2020-02-03 18:09 ` Michael Matz
2020-02-04 10:41 ` Andrew Stubbs
2020-02-03 18:57 ` Segher Boessenkool
2020-02-03 17:54 ` Richard Earnshaw (lists)
2020-02-03 18:20 ` Michael Matz
2020-02-03 19:48 ` Segher Boessenkool
2020-02-03 18:03 ` Joseph Myers
2020-02-03 17:34 ` Segher Boessenkool
2020-02-27 13:38 ` Nathan Sidwell
2020-03-02 13:01 ` Richard Earnshaw (lists)
2020-03-02 13:35 ` Segher Boessenkool
2020-03-02 14:31 ` Nathan Sidwell
2020-03-02 14:41 ` Jonathan Wakely
2020-03-02 15:22 ` Richard Earnshaw (lists)
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=8ae46cc6-d791-f84a-3230-27bed59f5844@arm.com \
--to=richard.earnshaw@arm.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jason@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).