From: Joe Perches <joe@perches.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Sep 27
Date: Fri, 27 Sep 2013 09:29:28 -0700 [thread overview]
Message-ID: <1380299368.17366.121.camel@joe-AO722> (raw)
In-Reply-To: <20130927190520.ab376c737166be4841ff46e4@canb.auug.org.au>
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?
next prev parent reply other threads:[~2013-09-27 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 9:05 linux-next: Tree for Sep 27 Stephen Rothwell
2013-09-27 16:29 ` Joe Perches [this message]
2016-09-27 6:40 Stephen Rothwell
2016-09-27 10:03 ` Sergey Senozhatsky
2016-10-04 0:48 ` Sergey Senozhatsky
2017-09-27 6:23 Stephen Rothwell
2018-09-27 5:45 Stephen Rothwell
2021-09-27 5:51 Stephen Rothwell
2022-09-27 20:10 broonie
2023-09-27 3:51 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1380299368.17366.121.camel@joe-AO722 \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).