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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <a781481a0706292029m31cf1295ie552bfc2707348cd@mail.gmail.com>
Date:	Sat, 30 Jun 2007 08:59:00 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
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 6/30/07, Satyam Sharma <satyam.sharma@...il.com> wrote:
> On 6/30/07, Kok, Auke <auke-jan.h.kok@...el.com> wrote:
> > [...]
> > 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.

Your idea is quite different though, of course.

> Hmm, associating MAINTAINERS and source files. I remember surfing LKML
> archives one day and coming across this huge and ugly flamefest when some
> guy called Eric S. Raymond (hehe :-) suggested something like this and got
> burned.

<ugh, reads again and feels stupid>

And before _I_ get burned for being impolite / provoking something, let me
clarify that the comment above was purely in spirit of humour (bad effort,
of course).
-
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/