From: Greg KH <gregkh@linuxfoundation.org>
To: Teck Choon Giam <giamteckchoon@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, Jiri Slaby <jslaby@suse.cz>,
stable@vger.kernel.org, lwn@lwn.net
Subject: Re: Linux 3.2.54
Date: Sat, 4 Jan 2014 09:32:10 -0800 [thread overview]
Message-ID: <20140104173210.GA32402@kroah.com> (raw)
In-Reply-To: <CAEwRVpN7z5rDnqNg3ZF+5=Go1EXKAm0TutQPUZ_mj2OCQ5-kwQ@mail.gmail.com>
On Sun, Jan 05, 2014 at 12:43:05AM +0800, Teck Choon Giam wrote:
> Hi Ben,
>
>
> On Fri, Jan 3, 2014 at 9:21 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > I'm announcing the release of the 3.2.54 kernel.
> >
> > All users of the 3.2 kernel series should upgrade.
> >
> > The updated 3.2.y git tree can be found at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.2.y
> > and can be browsed at the normal kernel.org git web browser:
> > http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git
>
>
> Just for your information,
> https://www.kernel.org/pub/linux/kernel/v3.x/ I can only see version
> 3.2.54 with tar.xz and tar.gz where tar.bz2 extension is missing. I
> don't know whether is this intentionally but just to let you know in
> case.
As was announced earlier, there will not be any more .bz2 tarballs
created starting this year, sorry. So this was intentional.
thanks,
greg k-h
next prev parent reply other threads:[~2014-01-04 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 13:21 Linux 3.2.54 Ben Hutchings
2014-01-04 16:43 ` Teck Choon Giam
2014-01-04 17:32 ` Greg KH [this message]
2014-01-04 18:38 ` Teck Choon Giam
2014-01-04 20:23 ` Gene Heskett
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=20140104173210.GA32402@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=giamteckchoon@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.