From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
To: trapdoor6@gmail.com
Cc: ramya.desai@gmail.com, horms@verge.net.au, linux-kernel@vger.kernel.org
Subject: Re: Where can I find -rc kernels?
Date: Mon, 01 Nov 2010 22:57:58 +0900 (JST) [thread overview]
Message-ID: <20101101.225758.12584142.ryusuke@osrg.net> (raw)
In-Reply-To: <AANLkTimqkGH3PMfyL02R9agaxbP9t+BzjqLUaPK=ynu8@mail.gmail.com>
On Mon, 1 Nov 2010 13:11:58 +0000, trapDoor <trapdoor6@gmail.com> wrote:
> On Mon, Nov 1, 2010 at 1:05 PM, trapDoor <trapdoor6@gmail.com> wrote:
> > On Mon, Nov 1, 2010 at 12:54 PM, Ramya Desai <ramya.desai@gmail.com> wrote:
> >> On Mon, Nov 1, 2010 at 5:46 PM, Simon Horman <horms@verge.net.au> wrote:
> >>>
> >>> Is this what you are after?
> >>>
> >>> http://www.kernel.org/pub/linux/kernel/v2.6/testing/
> >>
> >> Simon,
> >>
> >> 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
next prev parent reply other threads:[~2010-11-01 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 10:01 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 [this message]
2010-11-01 14:27 ` Ramya Desai
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=20101101.225758.12584142.ryusuke@osrg.net \
--to=konishi.ryusuke@lab.ntt.co.jp \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ramya.desai@gmail.com \
--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 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®