alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Florian Mickler <florian@mickler.org>
To: Joe Perches <joe@perches.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.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: Tue, 16 Nov 2010 18:37:07 +0100	[thread overview]
Message-ID: <20101116183707.179964dd@schatten.dmk.lab> (raw)
In-Reply-To: <1289919077.28741.50.camel@Joe-Laptop>

On Tue, 16 Nov 2010 06:51:17 -0800
Joe Perches <joe@perches.com> wrote:

> On Tue, 2010-11-16 at 10:49 +0000, Mark Brown wrote:
> > On Mon, Nov 15, 2010 at 11:52:53AM -0800, Joe Perches wrote:
> > > On Mon, 2010-11-15 at 19:34 +0000, Mark Brown wrote:
> > > > It appears your scripts are already hooked into get_maintainers.pl which
> > > > would seem the obvious place to do this?  Sadly I don't do perl, though
> > > > it looks like you're doing pretty much all the work on that anyway.
> > > Sadly, no it's not the right place.
> > To query MAINTAINERS?  I'd assume that's where you'd want to put that
> > stuff?
> 
> I trimmed cc's and added Andrew Morton and Florian Mickler.
> First thread link for them: http://lkml.org/lkml/2010/11/15/262
> 
> I use get_maintainer to find email addresses with
> "git send-email --cc-cmd=" but sure it could be extended
> to find some other new information in the MAINTAINERS file.
> 
> Anyway, I think that get_maintainers isn't the proper tool
> to rewrite commit subject lines, though it could certainly
> do the lookup of a key in the MAINTAINERS file.
> 
> Maybe add a new MAINTAINERS section line something like:
> 	"C:	CommitSubjectGrammarStyle"
> where CommitSubjectGrammarStyle is something more
> information rich than "style 1", "style 2".
> 
> Perhaps you'll propose a grammar to convert path to header
> and go through and add these "C:" style entries to the
> sections you maintain.
> 
> Also, what would you expect the output to be when a single
> patch modified files from 2 subsystems that use different
> styles?
> 
> cheers, Joe
> 

My first reaction to this is, it's silly. Certainly a
subsystem-maintainer is capable of hacking something together that
suits his needs or may just use a good editor to get the job done.
After all, he might want to edit the commit message anyway. Also he has
to have his act together for all non-conforming submitters anyway,
because shurely, telling people to re-edit their patches subject line
is not what one would consider "welcoming to newbies",  or whatever it
is kernel subsystem maintainers have to be nowadays *g*... 

On second thought, if that facility existed, i think nobody would mind
it either. So, why not. I don't see a way to specify what to do with
cross-subsystem patches though. 

(MAINTAINERS seems to be the logical place to put this
information.)

Regards,
Flo

  parent reply	other threads:[~2010-11-16 17:37 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 [this message]
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
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=20101116183707.179964dd@schatten.dmk.lab \
    --to=florian@mickler.org \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).