From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Sep 12
Date: Fri, 12 Sep 2014 10:39:19 -0700 [thread overview]
Message-ID: <54132FC7.1080004@infradead.org> (raw)
In-Reply-To: <20140912173817.3c719e7d@canb.auug.org.au>
On 09/12/14 00:38, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140911:
>
---------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).
No patch tarball?
--
~Randy
next prev parent reply other threads:[~2014-09-12 17:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-7062@linuxfoundation.org>
2014-09-12 7:38 ` linux-next: Tree for Sep 12 Stephen Rothwell
2014-09-12 17:39 ` Randy Dunlap [this message]
2014-09-13 1:59 ` Stephen Rothwell
2014-09-13 1:59 ` Stephen Rothwell
[not found] ` <rt-3.8.13-21049-1410573601-1407.7062-3-0@linuxfoundation.org>
[not found] ` <20140913120848.243db589@canb.auug.org.au>
2014-09-13 2:08 ` [Kernel.org Helpdesk #7062] AutoReply: " sfr@canb.auug.org.au via RT
2014-09-13 2:08 ` sfr@canb.auug.org.au via RT
2014-09-13 2:09 ` Stephen Rothwell
2025-09-12 5:16 Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 9:05 Stephen Rothwell
2023-09-12 5:26 Stephen Rothwell
2022-09-12 10:09 Stephen Rothwell
2018-09-12 4:39 Stephen Rothwell
2017-09-12 4:16 Stephen Rothwell
2017-09-12 13:18 ` Sergey Senozhatsky
2017-09-14 16:48 ` Andy Lutomirski
2017-09-14 22:31 ` Sergey Senozhatsky
2016-09-12 5:42 Stephen Rothwell
2015-09-12 5:09 Stephen Rothwell
2013-09-12 4:34 Stephen Rothwell
2013-09-12 4:34 ` 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=54132FC7.1080004@infradead.org \
--to=rdunlap@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.