public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@gentoo.org>
To: Michael Imhof <tantive@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] s390 status
Date: Mon, 20 Sep 2004 19:29:39 -0400	[thread overview]
Message-ID: <414F67E3.6080701@gentoo.org> (raw)
In-Reply-To: <414F4451.4010601@gentoo.org>

Why didn't you bring this up last week before we voted to drop s390 
support today?

Joshua

Michael Imhof wrote:

> 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.
>
>
> I think this one is not clear. Randy had access to it's "own" machine 
> where he did development etc.
> If access to an s390/zSeries is needed i can provide it.
> Randy and i had the idea of porting gentoo to zSeries and both got 
> access to different machines. The one from Randy was at his 
> university. The one i have access to is owned by a company that does 
> development for zSeries.
>
> The idea behind it was:
> Randy had a devlopment machine where he could tweak and work. When he 
> completed the first set of full stages we wanted to install Gentoo on 
> the Machine (better said partitions) i have access to and use those 
> partitions for providing access to s390 to devs.
>
>
> Another thing that makes me sad is that people who were very involved 
> in this port now have no problem to just let it die.
>
>
> So if there are ppl who want to maintain this port. Access to hardware 
> is here...
>
>
> Regards
> Michael



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-09-20 23:29 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
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 [this message]
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=414F67E3.6080701@gentoo.org \
    --to=method@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=tantive@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