From: Kim Nielsen <kn@insecurity.dk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo-sources vs "stock" kernels
Date: Thu, 23 Jan 2003 20:55:27 +0100 [thread overview]
Message-ID: <20030123195527.GB9824@localhost> (raw)
In-Reply-To: <030901c2c318$5d1390f0$0605010a@VELDYT>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
On Thu, Jan 23, 2003 at 01:48:12PM -0600, Thomas T. Veldhouse wrote:
> Now in reality ... Gentoo is bleeding edge (and I have seen bloodying on
> occasion) and it is up to the administrator to make sure that gentoo changes
> don't hose a production machine.
I agree, if the administrator want to run bleeding egde applikations and sometimes stability problems (Via packages that cannot compile) its up to the admin
/Kim
Ps. Don't send a message directly to me, I follow this list so I will see your message
>
[-- Attachment #2: Type: application/pgp-signature, Size: 200 bytes --]
next prev parent reply other threads:[~2003-01-23 20:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 19:05 [gentoo-dev] Gentoo-sources vs "stock" kernels Dewet Diener
2003-01-23 19:16 ` Peter Ruskin
2003-01-23 19:20 ` Kim Nielsen
2003-01-23 19:33 ` Dewet Diener
2003-01-23 19:41 ` Kim Nielsen
2003-01-23 19:48 ` Thomas T. Veldhouse
2003-01-23 19:55 ` Kim Nielsen [this message]
2003-01-23 20:02 ` Thomas T. Veldhouse
2003-01-23 20:08 ` Kim Nielsen
2003-01-23 20:21 ` Thomas T. Veldhouse
2003-01-23 21:25 ` Paul de Vrieze
2003-01-23 21:28 ` Thomas T. Veldhouse
2003-01-23 21:33 ` Paul de Vrieze
2003-01-23 21:41 ` Thomas T. Veldhouse
2003-01-23 21:20 ` Paul de Vrieze
2003-01-24 0:23 ` [gentoo-dev] Gentoo-sources vs "stock" kernels Troy Dack
2003-01-24 0:58 ` Thomas T. Veldhouse
2003-01-23 20:06 ` [gentoo-dev] Gentoo-sources vs "stock" kernels Mike Lundy
2003-01-25 2:04 ` Peter Ruskin
2003-01-23 19:34 ` Dylan Carlson
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=20030123195527.GB9824@localhost \
--to=kn@insecurity.dk \
--cc=gentoo-dev@gentoo.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