linux-kernel - Re: Linux 3.1-rc10

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Oct 2011 03:47:16 +0300
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Valdis.Kletnieks@...edu
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.1-rc10

On Sat, Oct 22, 2011 at 8:31 AM,  <Valdis.Kletnieks@...edu> wrote:
>
> Actually, the question was "Are there enough Linus cycles to do KS
> and all the merges in 2 weeks?". ;)

I think there will be.

The kernel summit is only two days, and then I have another day of
LinuxCon Europe, and basically a day of travel. So it's four days out
of the 2 weeks, and I can actually do the time-consuming part of the
merges while traveling (ie *looking* at them if I need to: the
technical merge action itself is usually never the problem).

Additionally, the first few days (which is KS/etc), I'll probably be
merging mainly from people who have already got k.org accounts because
they got into the trust network early, so it's going to be slightly
limited by the fact that it will invariably take some time to get the
gpg signing and k.org account setup a day or two.

So I'm not horribly worried.

What worries me more than the kernel summit is just that the 3.1
release cycle has dragged out longer than usual, so I'm a bit afraid
that the 3.2 merge window will just be more chaotic than usual just
because there might be more stuff there to be merged. But that's
independent of any KS issues, and I also suspect that the added time
for development has been largely nullified by the productivity lost
due to the k.org mess.

linux-next is pretty large, but I don't track historical sizes all
that well, so I can't say if it's noticeably larger than it usually
is. Stephen may know, but he's on vacation right now.

So we'll see.

                    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/