From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joe Perches <joe@perches.com>
Subject: Re: linux-next: Tree for Sep 27
Date: Fri, 27 Sep 2013 09:29:28 -0700
Message-ID: <1380299368.17366.121.camel@joe-AO722>
References: <20130927190520.ab376c737166be4841ff46e4@canb.auug.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Return-path: <linux-next-owner@vger.kernel.org>
Received: from smtprelay0087.hostedemail.com ([216.40.44.87]:35075 "EHLO
	smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL)
	by vger.kernel.org with ESMTP id S1751719Ab3I0Q3g (ORCPT
	<rfc822;linux-next@vger.kernel.org>);
	Fri, 27 Sep 2013 12:29:36 -0400
In-Reply-To: <20130927190520.ab376c737166be4841ff46e4@canb.auug.org.au>
Sender: linux-next-owner@vger.kernel.org
List-ID: <linux-next.vger.kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org

On Fri, 2013-09-27 at 19:05 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Heads up: I will be having a 3 week break leading up to the kernel
> summit.  This means that next-20130927 (today) will be the last
> linux-next release until next-20131028 (or maybe 29).  I presume that
> Linus will be up to v3.12-rc7 by then and -rc7 is often the last before
> a release ... Please plan accordingly.

Any thought of automating the -next aggregation and release
and letting any conflicts go unresolved during that time?