public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom McCabe <rocketjet314@yahoo.com>
To: linux-8086@vger.kernel.org
Subject: Re: Porting to different architectures
Date: Mon, 31 Jul 2006 19:57:34 -0700 (PDT)	[thread overview]
Message-ID: <20060801025734.53558.qmail@web51312.mail.yahoo.com> (raw)
In-Reply-To: <1154382255.7230.113.camel@localhost.localdomain>



--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> Ar Llu, 2006-07-31 am 21:47 +0200, ysgrifennodd
> Javier Sedano:
> > Hi,
> > 
> > Richard Wallman wrote:
> > > 
> > > There doesn't seem to be any of the project
> admins (the ones with the
> > > CVS SSH key) awake ATM - I was going to see if I
> could get a copy of the
> > > key so that *someone* could commit changes!
> Failing that, I would
> > > (reluctantly) have to fork the project just to
> keep things moving.
> > > 
> > 
> > 	I think there is a (slow, painful, bureaucratic)
> mechanism to retake 
> > abandoned projects. If you really want to do it,
> mail the sourceforge 
> > team to look for a solution.
> 
> If you plan to use it as the basis for a new OS for
> something else I
> would fork it. The existing project is as good as
> dead and it's probably
> easier to just turn it into what you need than worry
> about breaking the
> existing code.

Agreed. We can keep the current version for historical
purposes, and if someone wants to build a better OS
for ancient machines, there are more popular and
better designs than the 8088.

> Alan
> 
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

  reply	other threads:[~2006-08-01  2:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 14:09 Porting to different architectures chriscureau
2006-07-31 15:00 ` Hans
2006-07-31 15:35   ` Richard Wallman
2006-07-31 16:03     ` David Given
2006-07-31 16:24       ` Richard Wallman
2006-07-31 16:32         ` David Given
2006-07-31 17:42     ` Jody Bruchon
2006-08-01  6:49       ` Richard Wallman
2006-08-01 17:15         ` Segin
2006-07-31 19:47     ` Javier Sedano
2006-07-31 21:44       ` Alan Cox
2006-08-01  2:57         ` Tom McCabe [this message]
2006-08-01  5:27           ` Jody Bruchon
2006-08-01 13:22             ` Alan Cox
2006-08-01 14:41               ` Vikas N Kumar
2006-08-01 15:28                 ` Hans
2006-07-31 15:16 ` Petr Koval
2006-07-31 15:29   ` CVS access Mattia Jona-Lasinio
2006-07-31 15:43     ` Petr Koval
2006-07-31 15:51     ` Petr Koval
2006-08-02 13:24       ` Mattia Jona-Lasinio

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=20060801025734.53558.qmail@web51312.mail.yahoo.com \
    --to=rocketjet314@yahoo.com \
    --cc=linux-8086@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