From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 12
Date: Wed, 12 Oct 2011 08:26:05 -0700 [thread overview]
Message-ID: <4E95B18D.9070806@xenotime.net> (raw)
In-Reply-To: <20111012175425.a2e3e6e6a92265e433aeca25@canb.auug.org.au>
On 10/11/11 23:54, Stephen Rothwell wrote:
> Hi all,
>
> The linux-next tree is now available from
> git://github.com/sfrothwell/linux-next.git as a temporary measure while
> the kernel.org servers are unavailable.
>
> It may also turn up on git.kernel.org (depending on the mirroring). The
> patch is still absent, however.
>
> Changes since 20111011:
eh? I can't find it on github or kernel.org. what gives?
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-10-12 15:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 6:54 linux-next: Tree for Oct 12 Stephen Rothwell
2011-10-12 15:26 ` Randy Dunlap [this message]
2011-10-12 22:26 ` Stephen Rothwell
2011-10-12 22:31 ` Sedat Dilek
2011-10-13 0:46 ` linux-next: Tree for Oct 12 (sound/soc/codecs/wm1250-ev1) Randy Dunlap
2011-10-13 10:24 ` [alsa-devel] " Mark Brown
2011-10-13 18:28 ` Randy Dunlap
2011-10-13 21:58 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2012-10-12 7:30 linux-next: Tree for Oct 12 Stephen Rothwell
2015-10-12 8:30 Stephen Rothwell
2015-10-12 18:58 ` Sedat Dilek
2015-10-23 7:51 ` Sedat Dilek
2016-10-12 3:03 Stephen Rothwell
2018-10-12 7:43 Stephen Rothwell
2020-10-12 9:59 Stephen Rothwell
2021-10-12 9:46 Stephen Rothwell
2022-10-12 0:02 Stephen Rothwell
2023-10-12 5:43 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=4E95B18D.9070806@xenotime.net \
--to=rdunlap@xenotime.net \
--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 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).