From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965176AbeCGUY1 (ORCPT ); Wed, 7 Mar 2018 15:24:27 -0500 Received: from shards.monkeyblade.net ([184.105.139.130]:56760 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934959AbeCGUYZ (ORCPT ); Wed, 7 Mar 2018 15:24:25 -0500 Date: Wed, 07 Mar 2018 15:24:23 -0500 (EST) Message-Id: <20180307.152423.215706756372582141.davem@davemloft.net> To: paul@paul-moore.com Cc: lucien.xin@gmail.com, sfr@canb.auug.org.au, netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, richard_c_haines@btinternet.com Subject: Re: linux-next: manual merge of the selinux tree with the net-next tree From: David Miller In-Reply-To: References: <20180307.124500.1863183408172828694.davem@davemloft.net> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Paul Moore Date: Wed, 7 Mar 2018 15:20:33 -0500 > I suppose the right thing would have been for net-next > to pull selinux/next, yes? Nope.