All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramya Desai <ramya.desai@gmail.com>
To: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Cc: trapdoor6@gmail.com, horms@verge.net.au, linux-kernel@vger.kernel.org
Subject: Re: Where can I find -rc kernels?
Date: Mon, 1 Nov 2010 19:57:21 +0530	[thread overview]
Message-ID: <AANLkTi=fyNErf_mCi4hxUR12EdaUX5VaifC_j0dm8r1_@mail.gmail.com> (raw)
In-Reply-To: <20101101.225758.12584142.ryusuke@osrg.net>

On Mon, Nov 1, 2010 at 7:27 PM, Ryusuke Konishi
<konishi.ryusuke@lab.ntt.co.jp> wrote:

>> >> I did not find the complete sources in that link. I need complete
>> >> sources by which I can build the kernel images. OR Is there any
>> >> procedure for merging these changes into any stable kernel version
>> >> (2.6.36) for making it 2.6.37-rc1.
>> >>
>> >> Thanks and Regards,
>> >> Ramya.
>> >
>> > I guess It just hasn't been published there yet. Not present in git
>> > tree either - I still have 2.6.36-09871-g3985c7c and 'git pull' says:
>> > Already up-to-date.
>> >
>> It's out now at http://www.kernel.org/
>> But still can't pull it from git.
>> Thanks,
>> Tomasz
>
> v2.6.37-rc1 is in the git tree.
>
> It looks like only master branch hasn't been updated yet.
>
> Ryusuke Konishi

Dear All,

Thanks to every one.

The kernel version 2.6.37-rc1 is NOW available at
http://www.kernel.org/pub/linux/kernel/v2.6/testing/. I guess, it is
updated recently. Anyhow, thanks to all.

Thanks and Regards,
Ramya.

      reply	other threads:[~2010-11-01 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 10:01 Where can I find -rc kernels? Ramya Desai
2010-11-01 10:17 ` Justin P. Mattock
2010-11-01 12:16 ` Simon Horman
2010-11-01 12:54   ` Ramya Desai
2010-11-01 13:05     ` trapDoor
2010-11-01 13:11       ` trapDoor
2010-11-01 13:57         ` Ryusuke Konishi
2010-11-01 14:27           ` Ramya Desai [this message]

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='AANLkTi=fyNErf_mCi4hxUR12EdaUX5VaifC_j0dm8r1_@mail.gmail.com' \
    --to=ramya.desai@gmail.com \
    --cc=horms@verge.net.au \
    --cc=konishi.ryusuke@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trapdoor6@gmail.com \
    /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.