Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753966AbaJMNIG (ORCPT ); Mon, 13 Oct 2014 09:08:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36563 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753914AbaJMNIB (ORCPT ); Mon, 13 Oct 2014 09:08:01 -0400 From: Paul Moore To: James Morris Cc: Linus Torvalds , LSM List , Linux Kernel Mailing List , Stephen Rothwell Subject: Re: [GIT] Security subsystem upate for 3.18 Date: Mon, 13 Oct 2014 09:07:53 -0400 Message-ID: <6097685.yy4GYjPioe@sifl> Organization: Red Hat User-Agent: KMail/4.14.1 (Linux/3.16.1-gentoo; KDE/4.14.1; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, October 13, 2014 03:06:34 PM James Morris wrote: > On Sun, 12 Oct 2014, Linus Torvalds wrote: > > on some previous development, so it's often a good time to simply > > create a new feature branch. I don't know how James feels about > > merging multiple separate feature branches, but I know that *I* tend > > to appreciate it when I get multiple well-defined pull requests rather > > than one big one that does many different things. > > It's fine with me. > > This is the first time I saw (or noticed) that Paul had back merged ahead > of me, but it seemed to merge into my tree ok so I didn't query it at the > time. The management of the linux-security tree, the approach I was taking with the SELinux tree, and the approach that the other LSM maintainers use has been discussed many times on the LSM list. I'm also fairly certain that you were on the To/CC line for many, if not all, of those threads. -- paul moore security and virtualization @ redhat -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/