From: Oleg Verych <olecom@flower.upol.cz>
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 05:01:44 +0200 [thread overview]
Message-ID: <E1I4TDU-00023A-Nc@flower> (raw)
In-Reply-To: <20070630023451.GA21593@localdomain>
* Date: Sat, 30 Jun 2007 05:34:51 +0300
>
> 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.
LKML archive near you, search phrase "BTS", subjects that have
something about "the quality of the kernel". Good luck.
____
Description in other words. Forget about scripts in source tree, tracking
and management system (as already described) is needed.
--
-o--=O`C
#oo'L O
<___=E M
next prev parent reply other threads:[~2007-06-30 2:49 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 [this message]
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=E1I4TDU-00023A-Nc@flower \
--to=olecom@flower.upol.cz \
--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