From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Cc: Alexander Monakov <amonakov@ispras.ru>,
Gerald Pfeifer <gerald@pfeifer.com>,
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 17:17:00 -0000 [thread overview]
Message-ID: <20200203171703.GY22482@gate.crashing.org> (raw)
In-Reply-To: <a96e3375-4824-de4a-93ee-7667902449bf@arm.com>
On Mon, Feb 03, 2020 at 01:59:58PM +0000, Richard Earnshaw (lists) wrote:
> On 03/02/2020 13:54, Segher Boessenkool wrote:
> >None of this are *rules*. We should not pretend they are. An email
> >subject should be useful to what the receivers of that email use it for:
> >see if it very interesting to them, see if it probably not interesting
> >to them: that's the "smth: " at the start, and the PR number at the end,
> >and of course the actual subject itself, so we should not put in too
> >much fluff in the subject, there needs to be room left (in the less than
> >fifty chars total) for an actual subject :-)
> >
> >(The example in the patch does not capitalise the subject line, btw.
> >It should.)
>
> Where does your '50 chars' limit come from? It's not in the glibc text,
> and it's not in the linux kernel text either. AFAICT this is your
> invention and you seem to be the only person proposing it.
Ha, no.
It seems it originally is from
https://github.com/git/git/commit/927a503cd07718ea0f700052043f383253904a56
and it has been part of "man git commit" since
https://github.com/git/git/commit/936f32d3de468db8daf853155ddd5c6b191af60c
(2006 and 2007, resp.)
Segher
next prev parent reply other threads:[~2020-02-03 17:17 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)
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 [this message]
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=20200203171703.GY22482@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Richard.Earnshaw@arm.com \
--cc=amonakov@ispras.ru \
--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).