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>] [day] [month] [year] [list]
Date:	Thu, 12 Sep 2013 17:15:37 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Heads up about 3.12 merge window..

So this is just a heads-up that while I haven't actually closed the
merge window yet, I was really close to deciding to just make this one
a short one. I'm going to be on the road for the next few days and
then at LinuxCon US later next week, and I've tried very hard to merge
everything I had pending in time for that (despite my machine
mishaps).

And I have indeed merged everything that's come in, as far as I can
tell from the current state of my mailbox.

Now, what that means is that if you are a maintainer that hasn't
already sent in your pull request for 3.12, you had better have a good
excuse for why you left it until the last few days. On the other hand,
if you _have_ sent me a pull reqeust, and it hasn't shown up, ping me
separately, we've had those things caught in spam boxes etc, and I
might just have missed it.

Because if you don't have a good excuse and it's a big pull with lots
of development that you just left until very late in the merge window
to make it inconvenient for me, it's going to wait until 3.13.

Here's to hoping everybody just goes "Whew, good that I sent my pull
request early".

And in fact there really shouldn't be anything pending afaik. I've
already merged more commits than was in linux-next.

                  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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ