From: Cort Dougan <cort@fsmlabs.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: George France <france@handhelds.org>,
Thorsten Kranzkowski <dl8bcu@dl8bcu.de>,
axp-list mailing list <axp-list@redhat.com>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] eliminate compile warnings
Date: Sat, 9 Nov 2002 14:03:09 -0700 [thread overview]
Message-ID: <20021109140309.I15128@duath.fsmlabs.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0211092154230.20360-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Sat, Nov 09, 2002 at 09:55:52PM +0100
Some very long, and pointless, arguments can be had about which was
_first_. Lets talk about something more interesting - which ones are still
usable :) I do recall that Motorola Computer Group was very very unhappy
that an Alpha from DEC arrived for Linus before their PowerStack. Maybe
you can compare who shipped a machine to Linus first, then compare which
was powered on and so on.
I believe Linus only re-did the Alpha port. It was first done inside DEC.
They should get credit for getting on the Linux bandwagon early on.
} > If there is no entry in the MAINTAINERS file, then it is Linus. He did the Alpha port.
} > The first foray of Linux outside of the Intel architecture was to the Alpha processor.
}
} *beep* The m68k port is older, and IIRC the MIPS port is older as well. Those
} weren't started by Linus, though.
prev parent reply other threads:[~2002-11-09 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 21:47 [PATCH] eliminate compile warnings Thorsten Kranzkowski
2002-11-07 14:22 ` George France
2002-11-07 16:53 ` Jeff Garzik
2002-11-07 21:43 ` Thorsten Kranzkowski
2002-11-07 20:28 ` Thorsten Kranzkowski
2002-11-07 20:55 ` George France
2002-11-08 1:33 ` Richard Henderson
2002-11-08 2:54 ` George France
2002-11-08 3:25 ` Richard Henderson
2002-11-08 4:04 ` George France
2002-11-08 7:38 ` Thorsten Kranzkowski
2002-11-09 20:55 ` Geert Uytterhoeven
2002-11-09 21:03 ` Cort Dougan [this message]
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=20021109140309.I15128@duath.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=axp-list@redhat.com \
--cc=dl8bcu@dl8bcu.de \
--cc=france@handhelds.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.