linux-kernel - Re: [RFC] automatic CC generation for patch submission

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070630025425.59cbc299.akpm@linux-foundation.org>
Date:	Sat, 30 Jun 2007 02:54:25 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
Cc:	Dan Aloni <da-x@...atomic.org>,
	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] automatic CC generation for patch submission

On Fri, 29 Jun 2007 19:51:53 -0700 "Kok, Auke" <auke-jan.h.kok@...el.com> wrote:

> > 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.

We already have that information in git.  Parse the git changelogs of the
affected files, find out who works on them.

Not that it'll help much, given the amnount of stuff which gets
mysteriously ignored even when the correct people are cc'ed...

(For extra giggles we could parse emailed oops and bug reports and add the
appropriate cc's there too.  Harder.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/