From: Nathan Sidwell <nathan@acm.org>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org, GCC Development <gcc@gcc.gnu.org>
Subject: Re: [PATCH, v3] wwwdocs: e-mail subject lines for contributions
Date: Mon, 02 Mar 2020 14:31:00 -0000 [thread overview]
Message-ID: <d9d21624-2519-fff5-65b9-8171d7911634@acm.org> (raw)
In-Reply-To: <cba9b447-13dd-696c-2f2f-a1e68ace41ce@arm.com>
On 3/2/20 8:01 AM, Richard Earnshaw (lists) wrote:
> On 27/02/2020 13:37, Nathan Sidwell wrote:
>> On 2/3/20 6:41 AM, Richard Earnshaw (lists) wrote:
>>> On 22/01/2020 17:45, Richard Earnshaw (lists) wrote:
>>>>
>>>> [updated based on v2 discussions]
>>>>
>>>> This patch proposes some new (additional) rules for email subject lines
>>>> when contributing to GCC. The goal is to make sure that, as far as
>>>> possible, the subject for a patch will form a good summary when the
>>>> message is committed to the repository if applied with 'git am'. Where
>>>> possible, I've tried to align these rules with those already in
>>>> use for glibc, so that the differences are minimal and only where
>>>> necessary.
>>>>
>>>> Some things that differ from existing practice (at least by some
>>>> people)
>>>> are:
>>>>
>>>> - Use '<topic>:' rather than '[<topic>]'
>>>> - This is more git friendly and works with 'git am'.
>>>> - Put bug numbers at the end of the line rather than the beginning.
>>>> - The bug number is useful, but not as useful as the brief summary.
>>>> Also, use the shortened form, as the topic part is more usefully
>>>> conveyed in the proper topic field (see above).
>>>
>>> I've not seen any follow-up to this version. Should we go ahead and
>>> adopt this?
> I'd like to. But have we reached consensus? Seems that every time I
> produce a revised version of the text we end up in another round of bike
> shedding. (Is that a word?)
I'm not sure I've seen a specific proposal following yours. Some
suggestions for differences, with varying degrees of forcefulness. I
still say go for it.
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2020-03-02 14:31 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 10:43 [wwwdocs] Updates to contribute.html for git-friendly posting rules Richard Earnshaw (lists)
2020-01-19 14:47 ` Gerald Pfeifer
2020-01-20 11:54 ` Richard Earnshaw (lists)
2020-01-21 15:04 ` [PATCH, v2] wwwdocs: e-mail subject lines for contributions Richard Earnshaw (lists)
2020-01-21 15:10 ` Jakub Jelinek
2020-01-21 15:34 ` Richard Earnshaw (lists)
2020-01-21 16:26 ` Jakub Jelinek
2020-01-21 16:26 ` Richard Earnshaw (lists)
2020-01-21 18:32 ` Jason Merrill
2020-01-21 19:09 ` Richard Earnshaw (lists)
2020-01-22 9:35 ` Jakub Jelinek
2020-01-22 10:00 ` Richard Earnshaw (lists)
2020-01-22 10:04 ` Jakub Jelinek
2020-01-22 16:27 ` Richard Sandiford
2020-01-22 17:02 ` Marek Polacek
2020-01-22 17:10 ` Richard Earnshaw (lists)
2020-01-21 20:17 ` Segher Boessenkool
2020-01-22 10:14 ` Richard Earnshaw (lists)
2020-01-22 14:06 ` Segher Boessenkool
2020-01-22 19:15 ` [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)
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 [this message]
2020-03-02 14:41 ` Jonathan Wakely
2020-03-02 15:22 ` Richard Earnshaw (lists)
2020-02-03 15:34 ` [wwwdocs] Updates to contribute.html for git-friendly posting rules Segher Boessenkool
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=d9d21624-2519-fff5-65b9-8171d7911634@acm.org \
--to=nathan@acm.org \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.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).