From: Sedat Dilek <sedat.dilek@googlemail.com>
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 13
Date: Thu, 13 Oct 2011 11:38:19 +0200 [thread overview]
Message-ID: <CA+icZUUHG=FOuXyV9epL=OC8rCEv9LMUDZ0XJ1HhEsLrMMw_Qg@mail.gmail.com> (raw)
In-Reply-To: <20111013181606.a204565fad9caaa0fe680b75@canb.auug.org.au>
On Thu, Oct 13, 2011 at 9:16 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> The linux-next tree is still 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.
>
> Tomorrow will be the last linux-next release before (probably) November
> 1st (and therefore presumably the merge window for v3.2).
>
> Changes since 20111012:
>
[...]
> ----------------------------------------------------------------------------
>
> 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/v2.6/next/ ).
Just FYI...
http://www.kernel.org/pub/linux/kernel/v2.6/next/
Not Found
The requested URL /pub/linux/kernel/v2.6/next/ was not found on this server.
- Sedat -
next prev parent reply other threads:[~2011-10-13 9:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 7:16 linux-next: Tree for Oct 13 Stephen Rothwell
2011-10-13 9:38 ` Sedat Dilek [this message]
2011-10-13 22:08 ` [PATCH -next] infiniband: fix printk format in hw/nes_cm.c Randy Dunlap
2011-10-17 21:18 ` Roland Dreier
2014-10-13 4:33 linux-next: Tree for Oct 13 Stephen Rothwell
2014-10-13 5:37 ` Stephen Rothwell
2015-10-13 7:15 Stephen Rothwell
2016-10-13 2:31 Stephen Rothwell
2020-10-13 8:04 Stephen Rothwell
2021-10-13 6:05 Stephen Rothwell
2021-10-13 12:13 ` Rob Herring
2021-10-13 13:50 ` Corey Minyard
2021-10-13 14:47 ` Rob Herring
2022-10-13 2:49 Stephen Rothwell
2023-10-13 5:55 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='CA+icZUUHG=FOuXyV9epL=OC8rCEv9LMUDZ0XJ1HhEsLrMMw_Qg@mail.gmail.com' \
--to=sedat.dilek@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--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).