From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>,
torvalds@osdl.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [stable] Re: Linux 2.6.14.1
Date: Wed, 9 Nov 2005 11:19:56 +0800 [thread overview]
Message-ID: <2cd57c900511081919m2e704741j@mail.gmail.com> (raw)
In-Reply-To: <20051109021840.GB23537@kroah.com>
2005/11/9, Greg KH <greg@kroah.com>:
> On Wed, Nov 09, 2005 at 10:05:43AM +0800, Coywolf Qi Hunt wrote:
> > 2005/11/9, Greg KH <gregkh@suse.de>:
> > > We (the -stable team) are announcing the release of the 2.6.14.1 kernel.
> > >
> > > The diffstat and short summary of the fixes are below.
> > >
> > > I'll also be replying to this message with a copy of the patch between
> > > 2.6.14 and 2.6.14.1, as it is small enough to do so.
> > >
> > > The updated 2.6.14.y git tree can be found at:
> > > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/gregkh/linux-2.6.14.y.git
> > > and can be browsed at the normal kernel.org git web browser:
> > > www.kernel.org/git/
> >
> >
> > I'd appreciate it that if you would not overwrite the 2.6.14 record on
> > the kernel.org page, but add a new record for 2.6.14.y instead. It
> > would benefit others too. FYI: http://lkml.org/lkml/2005/10/9/18
>
> Sorry, but I am not in charge of that at all. Please contact the
> kernel.org web masters if you want to discuss this. And as 2.6.14 now
> has a documented security issue, I wouldn't recommend it being displayed
> on the kernel.org page anyway.
>
> Tools like ketchup can handle updating to the proper kernel version just
> fine if you want to use it, instead of having to rely on web pages :)
I tried a little. Nice tool! I have my own script with some of
ketchup's function partially for easy my lxr site maintaining. I'll
adapt my script to use it probably. Thanks.
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
next prev parent reply other threads:[~2005-11-09 3:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 1:07 Linux 2.6.14.1 Greg KH
2005-11-09 1:08 ` Greg KH
2005-11-09 2:05 ` Coywolf Qi Hunt
2005-11-09 2:18 ` [stable] " Greg KH
2005-11-09 3:19 ` Coywolf Qi Hunt [this message]
2005-11-09 2:22 ` Ernst Herzberg
2005-11-09 2:33 ` [stable] " Chris Wright
2005-11-09 2:40 ` Greg KH
2005-11-09 3:20 ` Ernst Herzberg
2005-11-09 5:13 ` Andrew Morton
2005-11-09 5:27 ` David S. Miller
2005-11-09 6:04 ` [stable] " Chris Wright
2005-11-09 11:57 ` Andrew Walrond
2005-11-09 16:45 ` Chris Wright
2005-11-09 17:15 ` Greg KH
2005-11-09 17:56 ` Andrew Walrond
2005-11-09 18:53 ` Bill Davidsen
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=2cd57c900511081919m2e704741j@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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