| 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
| ||
|
Message-ID: <53EF8AF2.2070605@fb.com> Date: Sat, 16 Aug 2014 12:46:42 -0400 From: Chris Mason <clm@...com> To: Linus Torvalds <torvalds@...ux-foundation.org> CC: linux-btrfs <linux-btrfs@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [GIT PULL] Smaller btrfs pull On 08/16/2014 11:11 AM, Linus Torvalds wrote: > On Fri, Aug 15, 2014 at 11:26 AM, Chris Mason <clm@...com> wrote: >> >> I've been running xfstests with these against your current git >> overnight, but I'm queueing up longer tests as well. I understand >> you may want to wait until rc2, but either way I'll get a sane queue >> into my linux-next branch for the rest of the rcs. > > You completely mis-understand. > > If something isn't appropriate for the merge window, then it sure as > HELL isn't appropriate for later rc's either. > > So I'm not going to pull some "stragglers" later and just pull some > initial stuff now. That's not how this works. Hi Linus, Sorry that I wasn't clear. I had already pushed 1/2 of the commits off to the 3.18 merge window. Of the remaining commits, my plan was to send the fixes that would qualify for rc2 or rc3 during those rcs. I was trying to say that I fully expected these patches to be closely inspected. I'll bring my white gloves. -chris -- 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