From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: alsa-devel@alsa-project.org, Jiri Kosina <trivial@kernel.org>,
linux-kernel@vger.kernel.org,
Florian Mickler <florian@mickler.org>,
Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: rfc: rewrite commit subject line for subsystem maintainer preference tool
Date: Tue, 16 Nov 2010 23:50:26 +0000 [thread overview]
Message-ID: <20101116235025.GA7256@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20101116152835.b0ab571c.rdunlap@xenotime.net>
On Tue, Nov 16, 2010 at 03:28:35PM -0800, Randy Dunlap wrote:
> On Tue, 16 Nov 2010 23:22:58 +0000 Mark Brown wrote:
> > On Tue, Nov 16, 2010 at 12:46:09PM -0800, Randy Dunlap wrote:
> > > Case usually doesn't matter to most of us.
> > Given that we're working in case sensitive languages here it's probably
> > safe to assume that a reasonable proportion of people will care; being
> > reasonably consistent with existing practice for the subsystem seems
> > sensible.
> Greg takes patches that say STAGING or Staging or staging.
> DaveM takes patches that say net: or netdev: or network: or NET:
> The sound maintainers take patches that say sound: or alsa: or ALSA:
> etc.
...and best practice would be to pay attention to what the standard
thing is for the subsystem and follow that. We shouldn't be suggesting
that people just ignore the case, though obviously if it's not clear
then it's not worth worrying too much about it.
next prev parent reply other threads:[~2010-11-16 23:50 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 [this message]
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
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=20101116235025.GA7256@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--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).