public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Dan Aloni <da-x@monatomic.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] automatic CC generation for patch submission
Date: Fri, 29 Jun 2007 19:51:53 -0700	[thread overview]
Message-ID: <4685C549.3020602@intel.com> (raw)
In-Reply-To: <20070630023451.GA21593@localdomain>

Dan Aloni wrote:
> Hello,
> 
> I'd like to present a suggestion for automatic generation of 
> carbon copy fields in the E-Mails of posted patches.
> 
> 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.
> 
> A posssible format for this file could be a newline-separated
> list of:
> 
>   [filename wildcard]:e-mail
> 
> For example, drivers/scsi/.maintainers would contain:
> 
>   libiscsi.*:open-iscsi@googlegroups.com
>   scsi_*.c:scsi-devel@vger.kernel.org
> 
>   etc...
> 
> Or, instead (or in addition) of having a '.maintainers' file 
> each directory we can modify source files by adding parsable 
> '/* MAINTAINER: name@domain */' comments. 
> 
> Some extensions to the popular E-Mail clients might be needed 
> here. Also, a bot reading LKML would automatically send links 
> about posted patches to the other mailing lists whenever 
> someone forgets to add a CC.
> 
> Any comments?

an easier way to implement this is to add an extra field in the MAINTAINERS 
file, something like below. All the contact info would stay the same, closely 
where applicable and it would allow you to also specify specific files as well.

Auke

(horribly whitespace-mutilated copy+paste from thunderbird below)

---
diff --git a/MAINTAINERS b/MAINTAINERS
index 4c3277c..e55be49 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -69,6 +69,7 @@ L: Mailing list that is relevant to this area
  W: Web-page with status/info
  T: SCM tree type and location.  Type is one of: git, hg, quilt.
  S: Status, one of the following:
+F: Directory tree or Files belonging to this subsystem

         Supported:      Someone is actually paid to look after this.
         Maintained:     Someone actually looks after it.
@@ -1880,6 +1881,7 @@ M:        auke-jan.h.kok@intel.com
  L:     e1000-devel@lists.sourceforge.net
  W:     http://sourceforge.net/projects/e1000/
  S:     Supported
+F:     drivers/net/e100.c

  INTEL PRO/1000 GIGABIT ETHERNET SUPPORT
  P:     Jeb Cramer
@@ -1895,6 +1897,7 @@ M:        auke-jan.h.kok@intel.com
  L:     e1000-devel@lists.sourceforge.net
  W:     http://sourceforge.net/projects/e1000/
  S:     Supported
+F:     drivers/net/e1000/

  INTEL PRO/10GbE SUPPORT
  P:     Jeff Kirsher
@@ -1910,6 +1913,7 @@ M:        auke-jan.h.kok@intel.com
  L:     e1000-devel@lists.sourceforge.net
  W:     http://sourceforge.net/projects/e1000/
  S:     Supported
+F:     drivers/net/ixgb/

  INTEL PRO/WIRELESS 2100 NETWORK CONNECTION SUPPORT
  P:     Yi Zhu

  reply	other threads:[~2007-06-30  2:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30  2:34 [RFC] automatic CC generation for patch submission Dan Aloni
2007-06-30  2:51 ` Kok, Auke [this message]
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
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=4685C549.3020602@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=da-x@monatomic.org \
    --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