From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: no release today
Date: Mon, 16 Sep 2019 06:05:14 +0100 [thread overview]
Message-ID: <D081BA7D-9074-441A-B6C3-A742B41FF111@canb.auug.org.au> (raw)
In-Reply-To: <20190916013727.GT4352@sirena.co.uk>
On 16 September 2019 2:37:27 am GMT+01:00, Mark Brown <broonie@kernel.org> wrote:
>On Thu, Sep 05, 2019 at 04:02:37PM +1000, Stephen Rothwell wrote:
>
>> As I said yesterday, there will be no release today, or any day until
>> September 30.
>
>I'm going to try to provide some builds for this week (16th-20th).
>There may also be a build for the 15th depending on how much rebuilding
>the rest of the trees is needed for the build I've got ongoing.
Hi Mark,
Thanks for this. Don't stress too much, it should ease off a bit when Linus
starts merging trees.
Cheers,
Stephen Rothwell
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2019-09-16 5:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 6:02 linux-next: no release today Stephen Rothwell
2019-09-16 1:37 ` Mark Brown
2019-09-16 5:05 ` Stephen Rothwell [this message]
2019-09-16 11:07 ` Mark Brown
2019-09-29 21:09 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-04-25 6:40 Stephen Rothwell
2021-05-31 7:36 Stephen Rothwell
2021-03-08 0:55 Stephen Rothwell
2020-12-02 6:29 Stephen Rothwell
2020-05-05 23:42 Stephen Rothwell
2020-03-09 2:35 Stephen Rothwell
2020-01-27 0:54 linux-next: No " Stephen Rothwell
2019-01-28 0:32 linux-next: no " Stephen Rothwell
2019-01-28 0:38 ` Gustavo A. R. Silva
2017-09-25 7:12 Stephen Rothwell
2017-09-25 7:35 ` Stephen Rothwell
2017-08-30 6:10 Stephen Rothwell
2017-08-14 2:03 Stephen Rothwell
2017-06-11 22:01 Stephen Rothwell
2016-11-07 5:16 Stephen Rothwell
2016-09-26 8:37 Stephen Rothwell
2016-08-10 8:19 Stephen Rothwell
2015-09-28 2:38 Stephen Rothwell
2014-07-22 6:49 Stephen Rothwell
2011-07-19 1:17 Stephen Rothwell
2010-09-21 22:26 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=D081BA7D-9074-441A-B6C3-A742B41FF111@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).