From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Florian Mickler <florian@mickler.org>,
Joe Perches <joe@perches.com>, Jiri Kosina <trivial@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: rfc: rewrite commit subject line for subsystem maintainer preference tool
Date: Wed, 17 Nov 2010 01:44:27 +0100 [thread overview]
Message-ID: <20101117014427.41d85b13@stein> (raw)
In-Reply-To: <20101116230126.GB24623@opensource.wolfsonmicro.com>
On Nov 16 Mark Brown wrote:
> On Tue, Nov 16, 2010 at 12:21:02PM -0800, Randy Dunlap wrote:
>
> > I don't know what you asked Joe to change, but asking someone to use
> > the documented canonical patch format:
>
> > <quote>
> > The canonical patch subject line is:
>
> > Subject: [PATCH 001/123] subsystem: summary phrase
> > </quote>
>
> > should be fine. And there is no need for printf-ish templates
> > for this in MAINTAINERS either.
>
> That's exactly what I asked him to do. He said he's not willing to use
> anything for "subsystem" which can't be automatically generated.
Why should we codify our conventions in MAINTAINERS to accommodate the
specific problem of virtually a _single_ patch author?
Conventions are living and are being adjusted all the time, as code
organization changes, people join and go, projects start and cease.
Said author please looks the conventions up in the git history. If he
finds that this decelerates his patch generation rate, he can surely
code a script that looks into git for him and suggests plausible
prefixes for his patch titles to him. Or he can collect a kind of
database (a config file) locally for his own use in which he records
conventional prefixes on the go.
--
Stefan Richter
-=====-==-=- =-== =---=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-11-17 0:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 3:04 [PATCH 00/44] remove unnecessary semicolons Joe Perches
2010-11-15 3:05 ` [PATCH 43/44] sound/core/pcm_lib.c: Remove " Joe Perches
2010-11-22 6:44 ` Takashi Iwai
2010-11-15 3:05 ` [PATCH 44/44] sound/soc/codecs: " Joe Perches
2010-11-15 11:09 ` Liam Girdwood
2010-11-15 13:49 ` Mark Brown
2010-11-15 17:09 ` Joe Perches
2010-11-15 17:30 ` Mark Brown
2010-11-15 17:34 ` Joe Perches
2010-11-15 18:27 ` Mark Brown
2010-11-15 18:30 ` Joe Perches
2010-11-15 19:07 ` Mark Brown
2010-11-15 19:14 ` Joe Perches
2010-11-15 19:34 ` Mark Brown
2010-11-15 19:52 ` Joe Perches
2010-11-16 10:49 ` Mark Brown
2010-11-16 14:51 ` rfc: rewrite commit subject line for subsystem maintainer preference tool Joe Perches
2010-11-16 15:04 ` Mark Brown
2010-11-16 17:37 ` Florian Mickler
2010-11-16 18:12 ` Mark Brown
2010-11-16 19:35 ` Florian Mickler
2010-11-16 19:55 ` Mark Brown
2010-11-16 20:21 ` Randy Dunlap
2010-11-16 20:42 ` Joe Perches
2010-11-16 20:46 ` Randy Dunlap
2010-11-16 23:22 ` Mark Brown
2010-11-16 23:28 ` Randy Dunlap
2010-11-16 23:50 ` Mark Brown
2010-11-16 23:57 ` Joe Perches
2010-11-17 0:55 ` Randy Dunlap
2010-11-16 23:57 ` Joe Perches
2010-11-16 23:01 ` Mark Brown
2010-11-17 0:44 ` Stefan Richter [this message]
2010-11-17 0:53 ` Jiri Kosina
2010-11-17 17:07 ` Mark Brown
2010-11-17 21:07 ` Stefan Richter
2010-11-17 23:49 ` Joe Perches
2010-11-17 19:32 ` [PATCH 44/44] sound/soc/codecs: Remove unnecessary semicolons Pavel Machek
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=20101117014427.41d85b13@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=florian@mickler.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=trivial@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).