From: Ned Ludd <solar@gentoo.org>
To: seemant@gentoo.org
Cc: gentoo-dev@lists.gentoo.org, g2boojum@gentoo.org
Subject: Re: [gentoo-dev] s390 status
Date: Sun, 19 Sep 2004 17:13:19 -0400 [thread overview]
Message-ID: <1095628399.20147.4839.camel@simple> (raw)
In-Reply-To: <1095616848.18232.1.camel@sephora>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
On Sun, 2004-09-19 at 14:00, Seemant Kulleen wrote:
> Before Randy left, he'd promised to give me access to his s390, but that
> never materialised, so at this point I'd say there's no access. Seeing
> as it's effectively an unmaintained port with no ETA on Randy, I say
> either remove s390 from KEYWORDS which it blocks or stable it and let
> the fallout happen when s390 returns to being an active port.
Letting it fallout would simplify the job of the security team. I think
we can/should revisit it and it's keywords when we have a developers and
some sort of resources other developers can test on/with.
Grant please add this as an item to discuss at Mondays meeting.
(Should we drop the s390 port for now?)
--
Ned Ludd <solar@gentoo.org>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-19 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 15:48 [gentoo-dev] s390 status Ciaran McCreesh
2004-09-19 18:00 ` Seemant Kulleen
2004-09-19 21:13 ` Ned Ludd [this message]
2004-09-19 21:23 ` Mike Frysinger
2004-09-19 22:14 ` Greg KH
2004-09-20 20:57 ` Michael Imhof
2004-09-20 23:29 ` Joshua Brindle
2004-09-21 0:14 ` Michael Imhof
2004-09-21 1:28 ` Mike Frysinger
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=1095628399.20147.4839.camel@simple \
--to=solar@gentoo.org \
--cc=g2boojum@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=seemant@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