From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756062AbaIRHMs (ORCPT ); Thu, 18 Sep 2014 03:12:48 -0400 Received: from tundra.namei.org ([65.99.196.166]:34461 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751279AbaIRHMr (ORCPT ); Thu, 18 Sep 2014 03:12:47 -0400 Date: Thu, 18 Sep 2014 17:12:36 +1000 (EST) From: James Morris To: David Howells cc: keyrings@linux-nfs.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] KEYS: Fixes for keyrings In-Reply-To: <2171.1410996444@warthog.procyon.org.uk> Message-ID: References: <23655.1410874187@warthog.procyon.org.uk> <24647.1410876063@warthog.procyon.org.uk> <2171.1410996444@warthog.procyon.org.uk> User-Agent: Alpine 2.11 (LRH 23 2013-08-11) MIME-Version: 1.0 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 Thu, 18 Sep 2014, David Howells wrote: > James Morris wrote: > > > No, if they go direct to Linus, they don't go into -next. > > Can you then sync your -next branch to Linus after Linus takes them please? Nope, I only want to sync on point releases unless absolutely necessary. -- James Morris