From: Sven Joachim <svenjoac@gmx.de>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Linux 3.0.2
Date: Tue, 16 Aug 2011 13:45:48 +0200 [thread overview]
Message-ID: <87pqk5h95f.fsf@turtle.gmx.de> (raw)
In-Reply-To: <4E4A5087.3040102@gmail.com> ("Török Edwin"'s message of "Tue, 16 Aug 2011 14:12:07 +0300")
On 2011-08-16 13:12 +0200, Török Edwin wrote:
> On 08/16/2011 04:54 AM, Greg KH wrote:
>> I'm announcing the release of the 3.0.2 kernel.
>>
>> All users of the 3.0 kernel series must upgrade.
>>
>> The updated 3.0.y git tree can be found at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-3.0.y.git
>> and can be browsed at the normal kernel.org git web browser:
>> http://git.kernel.org/?p=linux/kernel/git/stable/linux-3.0.y.git;a=summary
>>
>
> Kernel.org still shows 3.0.1, although the gitweb link points to the
> correct place repository and I can see 3.0.2 there.
There are already a gzip compressed tarball and patches in
kernel.org/pub/linux/kernel/v3.0/, but no bzip2 compressed versions.
> Is this some side-effect of switching to the linux-3.0.y.git
> repository? (the -2.6 stable repo is at 3.0.1).
I doubt that, since 3.0.1 had no such problems. And updated
tarballs/patches for 2.6.3[23]-longterm haven't appeared at all yet,
although those are in git as well. :-(
Cheers,
Sven
next prev parent reply other threads:[~2011-08-16 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 1:54 Linux 3.0.2 Greg KH
2011-08-16 1:55 ` Greg KH
2011-08-16 9:11 ` Jesper Juhl
2011-08-16 10:02 ` [stable] " Willy Tarreau
2011-08-16 11:35 ` Josh Boyer
2011-08-16 11:12 ` Török Edwin
2011-08-16 11:45 ` Sven Joachim [this message]
2011-08-16 13:58 ` Greg KH
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=87pqk5h95f.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=edwintorok@gmail.com \
--cc=gregkh@suse.de \
--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