linux-kernel - Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2

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: <46B8876C.70604@gmail.com>
Date:	Tue, 07 Aug 2007 16:53:32 +0200
From:	Rene Herman <rene.herman@...il.com>
To:	James Bottomley <James.Bottomley@...elEye.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2

On 08/07/2007 05:55 AM, James Bottomley wrote:

> I really, *really* think we need a pre-release tree that consists of all 
> the upstream targetted features (i.e. all of the for the next merge 
> window git trees) and nothing else.  -mm doesn't really satisfy this, 
> because it has so much other stuff that the people I need to get testing 
> this don't trust it.

I much agree with this. I used to run -mm at least somewhat frequently if it 
included stuff I was interested in (random features, or for example latest 
ALSA) but gave that up after I had it break on something unrelated and (to 
me) uninteresting a few times too many. There's so much in there that before 
you know it you end up spending time not on that which you wanted to spend 
time on but on something completely unrelated which given a fixed amount of 
available total time (and level/spread of knowledge/interest) gets to be a 
problem.

For latest ALSA, I now sometimes look at the ALSA repositories directly but 
otherwise it seems I'm not testing much of anything before late -rc's.

Not everything going to Linus gets there by way of -mm, but perhaps it could 
help if Andrew split off -merge from -mm, where -merge contained only stuff 
(from -mm) expected to go upstream in the next merge window.

Not sure if this is proposing that other people do more work -- wouldn't 
want do to anything of the sort...

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