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]

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

On Sat, 30 Jun 2007 13:47:52 +0300 Dan Aloni <da-x@...atomic.org> wrote:

> On Sat, Jun 30, 2007 at 02:54:25AM -0700, Andrew Morton wrote:
> > 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.
> 
> I think it's quite complex to make a reliable inference of maintainership 
> information from git.

Clever people will work it out.

> Given a set of historical modifiers of a file, 
> would you take the most common commiter(s), or the most common 
> _recent_ commiter(s), or what? It's a bit fuzzy.

All the above?  Multiply frequency by recency, pick the top five?

Doesn't matter much: the cost of picking too many is high.

I shudder at the thought of manually maintaining anything like this.

> Moreover, it is slow in comparison and assumes the availability of 
> local .git db, which wouldn't be the case for some porition of patch 
> submitters.

a) precalculate the tables once per week

b) the whole thing wouldn't succeed if it requires software at
   patch-submitter's site.  It'd need to run at vger.

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