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: <12c511ca0810151653p535d5ae4j297cf5b41900a4ba@mail.gmail.com>
Date:	Wed, 15 Oct 2008 16:53:51 -0700
From:	"Tony Luck" <tony.luck@...el.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"David Miller" <davem@...emloft.net>, alan@...rguk.ukuu.org.uk,
	greg@...ah.com, sfr@...b.auug.org.au, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: is the weeks before -rc1 the time to really be working on -next?

> Yes, but then people would end up being based on linux-next, and that's
> a pretty rubbery target with all the rebasing and trees getting
> dropped, etc.  And they'd accidentally end up having to actually
> compile and run linux-next, shock-horror-oh-the-humanity.

I built and booted linux-next a couple of times a week or so
for ia64.  Most of the time it worked just fine.  I found a few
build problems, but only three run-time problems. My boot
log shows 49 successful boots of linux-next based kernels
from 2.6.25-rc2 to 2.6.27-rc6

But perhaps less people are working on breaking ia64 :-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ