linux-kernel - Re: Slow DOWN, please!!!

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: <20080430155252.76469ead.akpm@linux-foundation.org>
Date:	Wed, 30 Apr 2008 15:52:52 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Willy Tarreau <w@....eu>
Cc:	torvalds@...ux-foundation.org, rjw@...k.pl, davem@...emloft.net,
	linux-kernel@...r.kernel.org, jirislaby@...il.com
Subject: Re: Slow DOWN, please!!!

On Thu, 1 May 2008 00:46:10 +0200
Willy Tarreau <w@....eu> wrote:

> On Wed, Apr 30, 2008 at 03:31:22PM -0700, Linus Torvalds wrote:
> > 
> > 
> > On Thu, 1 May 2008, Rafael J. Wysocki wrote:
> > > 
> > > > And there's no way to avoid the fact that during the merge window, we will 
> > > > get something on the order of ten thousand commits (eg 2.6.24->25-rc1 was 
> > > > 9629 commits).
> > > 
> > > Well, do we _have_ _to_ take that much?  I know we _can_, but is this really
> > > necessary?
> > 
> > Do you want me to stop merging your code?
> > 
> > Do you think anybody else does?
> > 
> > Any suggestions on how to convince people that their code is not worth 
> > merging?
> 
> I think you're approaching a solution Linus. If developers take a refusal
> as a punishment, maybe you can use that for trees which have too many
> unresolved regressions. This would be really unfair to subsystem maintainers
> which themselves merge a lot of work, but recursively they may apply the
> same principle to their own developers, so that everybody knows that it's
> not worth working on next code past a point where too many regressions are
> reported.
> 

Well.  If we were good enough at tracking bug reports and regressions we
could look at the status of subsytem X and say "no new features for you".

That would be a drastic step even if we had the information to do it (which
we don't).

It would certainly put the pigeon amongst the cats tho.
--
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/