LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-next <linux-next@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jun 5
Date: Mon, 8 Jun 2015 01:26:09 +1000 [thread overview]
Message-ID: <20150608012609.68ee8d35@canb.auug.org.au> (raw)
In-Reply-To: <1433513253.8590.5.camel@ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Hi Michael,
On Sat, 06 Jun 2015 00:07:33 +1000 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> So as Stephen said in his earlier email I did the linux-next merge today as a
> test run for when he's on vacation.
Thanks for that - you persisted longer that I would have :-)
> Also note the tree has moved, until I get permission on the official linux-next
> repo, for today it's at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux-next.git
I have pushed your updates into the official tree, now.
> I also don't have permission to upload the patch, so there is no patch today.
I also have not uploaded the patch (as I do not have the patch that you
created. It is not really an issue, but we can push that up later.
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
These should be up to date shortly.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-07 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 14:07 Michael Ellerman
2015-06-07 15:26 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-05 6:56 Stephen Rothwell
2019-06-05 6:14 Stephen Rothwell
2018-06-05 11:47 Stephen Rothwell
2017-06-05 7:19 Stephen Rothwell
2014-06-05 9:28 Stephen Rothwell
2013-06-05 5:36 Stephen Rothwell
2012-06-05 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=20150608012609.68ee8d35@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--subject='Re: linux-next: Tree for Jun 5' \
/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
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).