From: Sven Koch <haegar@sdinet.de>
To: "Randal, Phil" <prandal@herefordshire.gov.uk>
Cc: "Linux-Kernel (E-mail)" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH-RFC] README 1ST - New problem logging macros (2.5.38)
Date: Tue, 24 Sep 2002 16:15:42 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0209241613330.7015-100000@space.comunit.de> (raw)
In-Reply-To: <0EBC45FCABFC95428EBFC3A51B368C9501AF48@jessica.herefordshire.gov.uk>
On Tue, 24 Sep 2002, Randal, Phil wrote:
> You'll have to ask RedHat et al why they persist in backporting
> security patches to "old" releases of Apache (etc) instead of
> releasing the new versions. The effect is the same, with
> vulnerabilities being squashed, but the version numbers reported
> suggesting otherwise.
Because every new version gives you some new problems/incompatibilities,
which must not happen in a running production-environment.
And testing every security-update 4 weeks in the lab before putting
it into production would be worse.
c'ya
sven
--
The Internet treats censorship as a routing problem, and routes around it.
(John Gilmore on http://www.cygnus.com/~gnu/)
next prev parent reply other threads:[~2002-09-24 14:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 14:04 Randal, Phil
2002-09-24 14:15 ` Sven Koch [this message]
2002-09-26 15:43 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-09-24 4:56 Jeff Garzik
2002-09-24 4:49 Larry Kessler
2002-09-24 12:58 ` Denis Vlasenko
2002-09-24 13:59 ` Gerhard Mack
2002-09-24 22:38 ` Thunder from the hill
2002-09-24 1:55 Larry Kessler
2002-09-24 2:40 ` Jeff Garzik
2002-09-24 5:55 ` Rusty Russell
2002-09-24 6:11 ` Jeff Garzik
2002-09-24 6:58 ` Rusty Russell
2002-09-24 5:15 ` Greg KH
2002-09-24 5:28 ` Jeff Garzik
2002-09-26 18:56 ` Larry Kessler
2002-09-26 19:38 ` Rik van Riel
2002-09-26 20:01 ` Larry Kessler
2002-09-26 18:41 ` Rob Landley
2002-09-24 5:58 ` Greg KH
2002-09-24 16:32 ` Patrick Mochel
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=Pine.LNX.4.44.0209241613330.7015-100000@space.comunit.de \
--to=haegar@sdinet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=prandal@herefordshire.gov.uk \
/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®