public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: James Dabbs <JDabbs@TGA.com>
To: "ecos-discuss (E-Mail)" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] patches reviewed?
Date: Thu, 20 Jun 2002 15:32:00 -0000	[thread overview]
Message-ID: <F12384A3C489D411944100B0D07C673A45911D@NS1-2> (raw)


Gary Thomas <gary@chez-thomas.org> writes:

> I would suggest, for one thing, grabbing a good hostname that can be used
to host a web page, even if the provider/hosting
> service switches around.

I agree.  Even if a decision to use eCos is made on technical merits, it's
unknown current standing is enough of a problem for a product/program
manager to reach down and nix a decision to use it.  Before RedHat chucked
it, commercial OS companies already seemed to have a sales-call routine down
sling FUD if eCos came up ("eCos?  Oh that's just a shareware thing, isn't
it?").  Every day the ecos "brand" is in limbo, it will suffer in terms of
design wins, and ultimately, user community.

www.os-ecos.org and www.ecos-os.org are available.

James Dabbs, TGA

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2002-06-20 22:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 15:32 James Dabbs [this message]
2002-06-20 15:43 ` David N. Welton
2002-06-20 15:51 ` Scott Dattalo
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 10:46 Koeller, T.
2002-06-20 11:05 ` Jonathan Larmour
2002-06-20 13:35 ` Gary Thomas
2002-06-20 14:26   ` David N. Welton
2002-06-20 18:32     ` Jonathan Larmour
2002-06-20 18:28   ` Jonathan Larmour
2002-06-21  1:21   ` Holger Schurig

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=F12384A3C489D411944100B0D07C673A45911D@NS1-2 \
    --to=jdabbs@tga.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).