From: Dave Young <hidave.darkstar@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mm/-next release on kernel.org web page?
Date: Mon, 3 Aug 2009 09:54:21 +0800 [thread overview]
Message-ID: <a8e1da0908021854y489358f0s1bcf59825b422660@mail.gmail.com> (raw)
In-Reply-To: <20090803004836.12b2787f.sfr@canb.auug.org.au>
On Sun, Aug 2, 2009 at 10:48 PM, Stephen Rothwell<sfr@canb.auug.org.au> wrote:
> Hi Dave,
>
> On Sun, 2 Aug 2009 15:56:20 +0800 Dave Young <hidave.darkstar@gmail.com> wrote:
>>
>> Could you consider put mmtom release there just like before? And even
>> -next tree patchset? It will be more convenient for users who test
>> kernel just by downloading from web. Now it's impossible for them to
>> test these patchsets because they normally do not subscribe to lkml.
>
> Each -next release appears as a patch relatively to Linus' at
> http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/ . They
> come out basically each work day.
Thanks for tell, Actually I know this address. But we can not get it
from the www.kernel.org main page, isn't it? Could we put such link or
guide info in the main page along with other releases?
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
--
Regards
dave
next prev parent reply other threads:[~2009-08-03 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 7:56 Dave Young
2009-08-02 14:48 ` Stephen Rothwell
2009-08-03 1:54 ` Dave Young [this message]
2009-08-02 16:55 ` Randy Dunlap
2009-08-03 2:08 ` Dave Young
2009-08-03 2:30 ` Randy Dunlap
2009-08-03 5:01 ` J.H.
2009-08-27 0:42 ` J.H.
2009-08-27 3:33 ` Greg KH
2009-08-27 22:03 ` J.H.
2009-08-27 14:39 ` Dave Young
2009-08-27 19:43 ` Randy Dunlap
2009-08-27 20:57 ` J.H.
2009-08-27 21:46 ` Andrew Morton
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=a8e1da0908021854y489358f0s1bcf59825b422660@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®