Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753261Ab3I0Q3j (ORCPT ); Fri, 27 Sep 2013 12:29:39 -0400 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 ); Fri, 27 Sep 2013 12:29:36 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::,RULES_HIT:41:355:379:421:541:599:877:988:989:1260:1261:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1538:1593:1594:1711:1714:1730:1747:1777:1792:2198:2199:2393:2559:2562:2693:2828:3138:3139:3140:3141:3142:3351:3622:3673:3865:3866:3867:3868:3871:3874:4321:5007:7652:7903:10004:10400:10848:11232:11658:11914:12050:12517:12519:12555:12740:13069:13311:13357,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0 X-HE-Tag: fuel67_35cdebd3ffe5c X-Filterd-Recvd-Size: 1312 Message-ID: <1380299368.17366.121.camel@joe-AO722> Subject: Re: linux-next: Tree for Sep 27 From: Joe Perches To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Date: Fri, 27 Sep 2013 09:29:28 -0700 In-Reply-To: <20130927190520.ab376c737166be4841ff46e4@canb.auug.org.au> References: <20130927190520.ab376c737166be4841ff46e4@canb.auug.org.au> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.6.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 760 Lines: 18 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? -- 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/