public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
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: Sat, 30 Jun 2007 06:01:23 +0200	[thread overview]
Message-ID: <20070630040123.GI6087@stusta.de> (raw)
In-Reply-To: <20070630023451.GA21593@localdomain>

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.

And another important use case that shouldn't require much extra work 
would be to do the same for bug reports.

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.

> Dan Aloni

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2007-06-30  4:01 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
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 [this message]
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=20070630040123.GI6087@stusta.de \
    --to=bunk@stusta.de \
    --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