public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Security Advisories
Date: Sun Jul 29 18:45:02 2001	[thread overview]
Message-ID: <20010729184422.B14345@cvs.gentoo.org> (raw)
In-Reply-To: <1415.202.77.127.56.996453200.squirrel@mail.tendaweb.com>; from aies@tendaweb.com on Mon, Jul 30, 2001 at 07:33:20AM +0700

On Mon, Jul 30, 2001 at 07:33:20AM +0700, aies@tendaweb.com wrote:
> Hi all,
> Is there Gentoo Linux security advisories?
> 
> I think some people use Gentoo on their production server out there. They
> need security update for their server.

Well, we do not recommend Gentoo Linux for production environments at this
point, although several people may be using Gentoo Linux for such a purpose.
At 1.0, we'll have prompt security advisories.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			



  reply	other threads:[~2001-07-30  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-29 18:36 [gentoo-dev] Security Advisories aies
2001-07-29 18:45 ` Daniel Robbins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-29 18:32 aies

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=20010729184422.B14345@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@cvs.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