From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt
Date: Mon, 15 Apr 02 11:11:48 PDT [thread overview]
Message-ID: <0204151811.AA07988@ivan.Harhan.ORG> (raw)
Troy Benjegerdes <hozer@drgw.net> wrote:
> Above all, *readable* code, because otherwise someone changes something,
> and inadvertently breaks machines that they don't have to test on.
We've got this one settled in favor of ELF section magic to add machines, which
works for both of us.
> If better functionality for the user is your goal, you can't achieve it by
> designing code around that goal. (Unless, of course, you're Apple computer
> and have large resources for QA and testing, and design the hardware
> yourself)
I do design the hardware myself now. But the company I take example from is
DEC, not Apple.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-04-15 18:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 18:11 Michael Sokolov [this message]
2002-04-16 23:16 ` 2.5 (or beyond) arch-specific boot modules Troy Benjegerdes
[not found] <200204060739.g367duV18841@helium.Harhan.ORG>
2002-04-08 15:20 ` Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt Tom Rini
2002-04-08 17:58 ` benh
2002-04-08 18:57 ` Tom Rini
2002-04-08 18:40 ` Benjamin Herrenschmidt
2002-04-09 8:14 ` Geert Uytterhoeven
2002-04-09 10:08 ` benh
[not found] ` <0204081705.AA21087@ivan.Harhan.ORG>
2002-04-08 18:02 ` benh
2002-04-09 14:52 ` Tom Rini
2002-04-09 19:23 ` Michael Sokolov
2002-04-09 19:47 ` Tom Rini
2002-04-09 20:05 ` Michael Sokolov
2002-04-09 20:15 ` Daniel Jacobowitz
2002-04-10 15:09 ` Tom Rini
2002-04-11 3:11 ` Michael Sokolov
2002-04-11 15:29 ` Tom Rini
2002-04-15 16:54 ` Troy Benjegerdes
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=0204151811.AA07988@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).