public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: John Bradford <john@grabjohn.com>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Release of 2.4.21
Date: 21 Mar 2003 22:53:40 +0100	[thread overview]
Message-ID: <1048283620.15199.22.camel@sonja> (raw)
In-Reply-To: <200303210923.h2L9NciG000393@81-2-122-30.bradfords.org.uk>

[-- Attachment #1: Type: text/plain, Size: 561 bytes --]

Am Fre, 2003-03-21 um 10.23 schrieb John Bradford:

> Unless the system has to run 24/7, which a desktop machine usually
> doesn't have to, I don't see why testing 2.5 on it isn't a
> possibility.

Because desktop systems usually don't feature the notion of a testbed,
read an environment in which dangerous changes can be tested without
severe loss of important data.

I would never ever boot a 2.5.x kernel on my notebook or on any other 
machines without preparing a different harddrive for instance, YMMV
though.

-- 
Servus,
       Daniel

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-03-21 22:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 19:56 Release of 2.4.21 Adrian Knoth
2003-03-20 20:21 ` Sebastian D.B. Krause
2003-03-20 20:34   ` Jeff Garzik
2003-03-20 20:42     ` Christoph Hellwig
2003-03-20 20:53       ` Jeff Garzik
2003-03-20 21:05         ` David Lang
2003-03-21  1:55       ` Andrew Morton
2003-03-21  0:13         ` John Bradford
2003-03-21  1:30           ` Samuel Flory
2003-03-21  9:33             ` John Bradford
2003-03-21  8:40           ` Bernd Petrovitsch
2003-03-21  9:23             ` John Bradford
2003-03-21 21:53               ` Daniel Egger [this message]
2003-03-22  8:27                 ` John Bradford
2003-03-22 14:54                   ` Daniel Egger
2003-03-21  1:01 ` Alan Cox
2003-03-21  0:04   ` David Lang
     [not found] <20030320200019$6ddc@gated-at.bofh.it>
     [not found] ` <20030320203015$4839@gated-at.bofh.it>
2003-03-20 20:43   ` Florian Weimer
2003-03-20 21:03     ` Jeff Garzik
2003-03-20 21:33       ` H. Peter Anvin
2003-03-20 22:08       ` Sebastian D.B. Krause
2003-03-21 11:06         ` Oliver Feiler
2003-03-20 22:18       ` Arador
2003-03-21  1:20       ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2003-03-20 21:17 Dow, Benjamin
2003-03-21  0:57 ` Alan Cox
     [not found] <20030320205011$1378@gated-at.bofh.it>
     [not found] ` <20030320205011$0acb@gated-at.bofh.it>
     [not found]   ` <20030320205011$2c88@gated-at.bofh.it>
     [not found]     ` <20030320211011$5967@gated-at.bofh.it>
2003-03-20 21:48       ` Florian Weimer

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=1048283620.15199.22.camel@sonja \
    --to=degger@fhm.edu \
    --cc=john@grabjohn.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