public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: davidw@dedasys.com (David N. Welton)
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] eCos developpement process?
Date: Fri, 21 Nov 2003 10:09:00 -0000	[thread overview]
Message-ID: <87r802rqai.fsf@dedasys.com> (raw)
In-Reply-To: <20031121095738.GE9114@lunn.ch>

Andrew Lunn <andrew@lunn.ch> writes:

> Big patches take more work and so tend to take longer. Ugly patches
> generally either get rejected and requested to be re-written, or we
> fix them ourselves.  Some patches get stuck for legal reasons. Some
> patches get included fast because it interests a particular
> maintainers. Some patches get delayed because no maintainer is
> particularly interested in the patch.

It's almost completely slipped my mind at this point, because I
haven't touched eCos since then, but which combination of these
factors best describe the floppy driver that I had posted?

Thankyou,
-- 
David N. Welton
   Consulting: http://www.dedasys.com/
     Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/

-- 
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-21 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  9:34 Vincent Catros
2003-11-21  9:57 ` Andrew Lunn
2003-11-21 10:09   ` David N. Welton [this message]
2003-11-21 10:34     ` Andrew Lunn
2003-11-21 12:08   ` [ECOS] " Daniel Néri
2003-11-21 12:53   ` [ECOS] RE : [ECOS] " Vincent Catros
2003-11-21 13:15     ` Andrew Lunn

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=87r802rqai.fsf@dedasys.com \
    --to=davidw@dedasys.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).