public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Adrian Caceres <adrian@atheros.com>
Cc: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] ECOS development model
Date: Tue, 11 Nov 2003 07:46:00 -0000	[thread overview]
Message-ID: <20031111074636.GB31822@lunn.ch> (raw)
In-Reply-To: <3FB03907.1070604@atheros.com>

On Mon, Nov 10, 2003 at 05:19:03PM -0800, Adrian Caceres wrote:
> I was a tad surprised by the answer below regarding what version of ECOS 
> should an
> app developer use so I was wondering what did I miss:
> 
> - What is open source community development model for  ECOS?

This thread kind of answers your question. 

http://sources.redhat.com/ml/ecos-discuss/2003-09/msg00388.html

        Andrew

-- 
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:[~2003-11-11  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06 18:10 [ECOS] Redboot image load via PCI bus? Snider, Marc
2003-11-06 18:13 ` Gary Thomas
2003-11-11  1:19   ` [ECOS] ECOS development model Adrian Caceres
2003-11-11  7:46     ` Andrew Lunn [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=20031111074636.GB31822@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=adrian@atheros.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).