From: Dan Aloni <da-x@monatomic.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@uk.ibm.com>
Subject: Re: [RFC] automatic CC generation for patch submission
Date: Sat, 30 Jun 2007 12:47:11 +0300 [thread overview]
Message-ID: <20070630094711.GB1297@localdomain> (raw)
In-Reply-To: <20070630040123.GI6087@stusta.de>
On Sat, Jun 30, 2007 at 06:01:23AM +0200, Adrian Bunk wrote:
> On Sat, Jun 30, 2007 at 05:34:51AM +0300, Dan Aloni wrote:
> >...
> > Basically, instead of manually figuring out who to add to CC
> > when sending a patch to LKML by looking at MAINTAINERS, a
> > script can look at '.maintainers' files spread across the
> > source tree and automatically generate a proper list of CCs
> > for a patch.
> >...
> > To illustrate: If a patch affects a file under
> > drivers/net/e1000, the CC script will look at these files
> >
> > drivers/net/e1000/.maintainers
> > drivers/net/.maintainers
> > drivers/.maintainers
> > .maintainers
> >
> > ... to gather up the mailing list addresses or an individual
> > maintainer inbox address.
> >...
> > Any comments?
>
> As Auke said, maintaining the information in MAINTAINERS would be
> better.
Yes, I tend to agree.
> And another important use case that shouldn't require much extra work
> would be to do the same for bug reports.
Yes, however for bug reports it isn't always possible to tell which
subsystem or files would get fixed once the bug is understood.
Perhaps it would be good once the bug report reaches the stage where
patches are made.
> Generally, you should keep in mind that it must fit into the workflow of
> the people who should use it. E.g. I could imagine that it might make
> more sense if you write a small tool that takes a patch or a path and
> outputs email addresses instead of a huge tool that tries to solve too
> many problems at once and doesn't fit into the workflow of most people.
I absolutely agree - in fact I was thinking of this as a nice
addition to scripts/checkpatch.pl. For example:
Your patch has no obvious style problems and is ready for submission.
When submitting this particular patch, you should CC to:
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
However my Perl hacking capabilities (or incapabilities thereof)
wouldn't do good to that script I suppose.
--
Dan Aloni
XIV LTD, http://www.xivstorage.com
da-x (at) monatomic.org, dan (at) xiv.co.il
next prev parent reply other threads:[~2007-06-30 9:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 2:34 Dan Aloni
2007-06-30 2:51 ` Kok, Auke
2007-06-30 3:10 ` Satyam Sharma
2007-06-30 3:29 ` Satyam Sharma
2007-06-30 9:54 ` Andrew Morton
2007-06-30 10:47 ` Dan Aloni
2007-06-30 16:32 ` Andrew Morton
2007-06-30 17:20 ` Adrian Bunk
2007-06-30 17:21 ` Dan Aloni
2007-06-30 14:33 ` Kok, Auke
2007-06-30 3:01 ` Oleg Verych
2007-06-30 3:08 ` Dan Aloni
2007-06-30 10:22 ` Oleg Verych
2007-06-30 10:26 ` Dan Aloni
2007-06-30 11:03 ` Oleg Verych
2007-06-30 4:01 ` Adrian Bunk
2007-06-30 9:47 ` Dan Aloni [this message]
2007-06-30 12:26 ` Adrian Bunk
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=20070630094711.GB1297@localdomain \
--to=da-x@monatomic.org \
--cc=apw@uk.ibm.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®