linux-kernel - Re: Linux 2.6.24

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: <alpine.LFD.1.00.0801241529440.15329@hp.linux-foundation.org>
Date:	Thu, 24 Jan 2008 15:41:08 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.24

On Thu, 24 Jan 2008, Linus Torvalds wrote:
> 
> The release is out there (both git trees and as tarballs/patches), and for 
> the next week many kernel developers will be at (or flying into/out of) 
> LCA in Melbourne, so let's hope it's a good one.

Since I already had two kernel developers asking about the merge window 
and whether people (including me) traveling will impact it, the plan right 
now is to keep the impact pretty minimal. So yes, it will probably extend 
the window from the regular two weeks, but *hopefully* not by more than a 
few days.

I'm going to try to merge at least some stuff while I'm in Melbourne, and 
I'd expect that most of the stuff that happens during LCA is code that is 
already pending to be merged (that's how the merge window is _supposed_ to 
work, after all, but with the 2.6.24 release cycle being longer than usual 
I suspect it's actually true in practice too).

And the second week of the merge window I'll be back again.

If I have bad bandwidth or am just goofing off during LCA, or if I end up 
being too jetlagged to merge well after, that will obviously push out 
things. And the same thing obviously goes for any other maintainer in the 
same condition. 

I'd hope that the git users to be in fairly good condition (with hopefully 
much of the stuff pending for 2.6.25 ready to go), and would worry more 
about people like Andrew in particular. So let's see how this works out.

In short: I'm hoping that there won't be a big impact, but hey, let's be 
flexible. Who knows what happens..

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