From: Greg KH <gregkh@suse.de>
To: Teck Choon Giam <giamteckchoon@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.33.10
Date: Fri, 15 Apr 2011 13:40:45 -0700 [thread overview]
Message-ID: <20110415204045.GA22823@suse.de> (raw)
In-Reply-To: <BANLkTi=H964m-34b9QOR_X52j0Drz8fKzg@mail.gmail.com>
On Sat, Apr 16, 2011 at 01:39:00AM +0800, Teck Choon Giam wrote:
> On Sat, Apr 16, 2011 at 1:36 AM, Teck Choon Giam
> <giamteckchoon@gmail.com> wrote:
> > HI Greg,
> >
> > Many thanks for your time to maintain this longterm kernel version.
> >
> > Wonder why there isn't a full source tarball available for download?
> >
> > wget http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.32/linux-2.6.32.37.tar.bz2
> > --2011-04-16 01:30:46--
> > http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.32/linux-2.6.32.37.tar.bz2
> > Resolving www.kernel.org... 199.6.1.164, 130.239.17.4, 149.20.4.69, ...
> > Connecting to www.kernel.org|199.6.1.164|:80... connected.
> > HTTP request sent, awaiting response... 404 Not Found
> > 2011-04-16 01:30:49 ERROR 404: Not Found.
> >
> > I noticed the commit in this git tree is dated 14th so must I wait a
> > little longer for the full source tarball to be available?
> >
> > Thanks.
> >
> > Kindest regards,
> > Giam Teck Choon
> >
>
> Ops... sorry, should have post under Linux 2.6.32.37 thread instead.
> Anyway, same thing for Linux 2.6.33.10 :)
The mirroring sometimes takes a while to sync up, the files look to be
there now, right?
thanks,
greg k-h
next prev parent reply other threads:[~2011-04-15 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 16:49 Linux 2.6.33.10 Greg KH
2011-04-15 16:50 ` Greg KH
2011-04-15 17:36 ` Teck Choon Giam
2011-04-15 17:39 ` Teck Choon Giam
2011-04-15 20:40 ` Greg KH [this message]
2011-04-15 21:24 ` Teck Choon Giam
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=20110415204045.GA22823@suse.de \
--to=gregkh@suse.de \
--cc=giamteckchoon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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).