linux-kernel - Re: Linux 3.15-rc8 ... and merge window for 3.16

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]

Message-ID: <20140602214019.GA2134@redhat.com>
Date:	Mon, 2 Jun 2014 17:40:19 -0400
From:	Dave Jones <davej@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.15-rc8 ... and merge window for 3.16

On Sun, Jun 01, 2014 at 07:37:20PM -0700, Linus Torvalds wrote:
 > So let's try to see how well that works - the last weeks of the
 > release tends to be me just waiting around to make sure nothing bad is
 > happening, so doing this kind of overlapping development *should* work
 > fine. Maybe it works so well that we'll end up doing it in the future
 > even if there *isn't* some kind of scheduling conflict that makes me
 > want to start the merge window before I'm 100% comfortable doing the
 > release for the previous version.

one side-effect of this is that the git-commits-head list is now posting
the commits you're queueing in your next branch but no way afaict to
distinguish them from changes going into 3.15

Can whoever maintains that hook add an X-branch header or something to make
filtering them easier ?

	Dave

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