From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 16
Date: Thu, 17 Nov 2016 09:54:58 +1100 [thread overview]
Message-ID: <20161117095458.36c19852@canb.auug.org.au> (raw)
In-Reply-To: <20161116152445.7a7902f6@canb.auug.org.au>
Hi all,
On Wed, 16 Nov 2016 15:24:45 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Changes since 20161115:
>
> Non-merge commits (relative to Linus' tree): 5617
> 5979 files changed, 365287 insertions(+), 131171 deletions(-)
I forgot to mention that there will be no linux-next releases on Friday
(tomorrow) or Monday.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-11-16 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 4:24 linux-next: Tree for Nov 16 Stephen Rothwell
2016-11-16 22:54 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-16 2:17 Stephen Rothwell
2022-11-16 6:51 Stephen Rothwell
2021-11-16 2:19 Stephen Rothwell
2020-11-16 6:59 Stephen Rothwell
2018-11-16 5:43 Stephen Rothwell
2017-11-16 4:00 Stephen Rothwell
2015-11-16 3:11 Stephen Rothwell
2011-11-16 2:33 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=20161117095458.36c19852@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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