From: Dan Malek <dan@netx4.com>
To: diekema_jon <diekema@bucks.si.com>
Cc: Ruedi.Hofer@ascom.ch, linuxppc-embedded@lists.linuxppc.org,
all@cideas.com
Subject: Re: Current state of MPC8260 Linux
Date: Wed, 23 Feb 2000 12:08:52 -0500 [thread overview]
Message-ID: <38B41424.8921DC4@netx4.com> (raw)
In-Reply-To: m12NRsU-001SwhC@bucks
diekema_jon wrote:
> If anyone has additional wisdom on this topic,
There are people that profusely contribute Open Source software
without complaint, providing clever designs and elegant software
style. These people have my greatest respect and deepest
gratitude. I am striving to be like them.
Some of us contribute to the best of our ability, fortunate to
have others realize our value to their success. To pay our
bills in life, we have agreed to provide production quality
software for their products. Ultimately, indirectly, albeit
more slowly, they too contribute Open Source software.
Others believe the Open Source train isn't stopping at their
station, failing to realize bleeding edge technology requires
resource investments commensurate with their expected rewards.
Their product development will fail due to the lack of exercising
options that reduce development risk and ensure success. They
are unlikely to benefit from or contribute Open Source software.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-23 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0FQB00A8FULE7R@pmdf-it.hasler.ascom.ch>
2000-02-23 2:50 ` Current state of MPC8260 Linux diekema_jon
2000-02-23 17:08 ` Dan Malek [this message]
2000-02-23 19:38 ` PPC403 bootup problem Tom Shaver
2000-02-23 21:41 ` Grant Erickson
2000-03-16 21:42 ` Linux Planet Module Support Jo-Ellen F. Mathews
2000-03-16 22:05 ` Joe Green
2000-03-16 22:45 ` Pavel Roskin
2000-02-23 19:58 ` Current state of MPC8260 Linux Gilbert Coville
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=38B41424.8921DC4@netx4.com \
--to=dan@netx4.com \
--cc=Ruedi.Hofer@ascom.ch \
--cc=all@cideas.com \
--cc=diekema@bucks.si.com \
--cc=linuxppc-embedded@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).