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 Jan 29
Date: Wed, 29 Jan 2014 16:30:27 +1100 [thread overview]
Message-ID: <20140129163027.50f4184a6c57c67079b46bb5@canb.auug.org.au> (raw)
In-Reply-To: <20140129162855.d232e4d964107fd3ce0ca5d8@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
On Wed, 29 Jan 2014 16:28:55 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Non-merge commits (relative to Linus' tree): 2689
> 3435 files changed, 215376 insertions(+), 61940 deletions(-)
Actually:
Non-merge commits (relative to Linus' tree): 2751
3315 files changed, 222970 insertions(+), 63268 deletions(-)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-29 5:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 5:28 linux-next: Tree for Jan 29 Stephen Rothwell
2014-01-29 5:30 ` Stephen Rothwell [this message]
2015-01-29 8:11 Stephen Rothwell
2016-01-29 4:10 Stephen Rothwell
2018-01-29 8:54 Stephen Rothwell
2019-01-29 6:11 Stephen Rothwell
2020-01-29 4:54 Stephen Rothwell
2024-01-29 3:30 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=20140129163027.50f4184a6c57c67079b46bb5@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;
as well as URLs for NNTP newsgroup(s).