linux-kernel - Re: [PATCH] gpiolib: Allow user-selection

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: <486C8F9C.7080507@keyaccess.nl>
Date:	Thu, 03 Jul 2008 10:36:44 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	David Brownell <david-b@...bell.net>,
	Michael Buesch <mb@...sch.de>, sfr@...b.auug.org.au,
	linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>
Subject: Re: [PATCH] gpiolib: Allow user-selection

On 03-07-08 07:08, Andrew Morton wrote:

> But what I am repeatedly seeing is people cheerfully raising 2.6.27 
> patches against the 2.6.26 tree when we have a nice 2.6.27 tree for 
> developing against.  Those days are over, guys.
> 
> I'm also seeing obvious signs that developers aren't _testing_ their 
> new code within the context of the 2.6.27 tree.  They're obviously 
> testing their stuff against 2.6.26 and then hoping and praying, only
> it doesn't always work out for them.

Developing against -next is even worse than developping against an -rc1. 
You normally want to be running the code you develop meaning you'd very 
frequently drown in everyone else's bugs without getting to your own if 
you do. Development needs to happen against something relatively stable 
really and the last release would generally seem to be the best choice.

Now ofcourse, _porting_ it to -next before submitting makes lots of 
sense but positioning -next as THE devel tree a bit less I feel...

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/