From: Andrew Lunn <andrew@lunn.ch>
To: Vincent Catros <Vincent.Catros@elios-informatique.fr>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] eCos developpement process?
Date: Fri, 21 Nov 2003 09:57:00 -0000 [thread overview]
Message-ID: <20031121095738.GE9114@lunn.ch> (raw)
In-Reply-To: <000701c3b013$1cd23030$7407a8c0@figuier>
On Fri, Nov 21, 2003 at 10:37:43AM +0100, Vincent Catros wrote:
> I know that mailing list is the prefered way to submit new packages and
> bud fixes. But then, who decide to include it in the official eCos
> distribution and how long it takes?
The maintainers decide what is included. How long a particular patch
takes to be included varies for a number of reasons. 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.
Maintainers do there work totally voluntary, in the spare time etc. We
have a RealLife(tm) as well to lead, some sometimes patches get delayed
because we spend a weekend skiing, or flying our plane, etc....
> This question comes because I've been faced to a bug with JFFS2.
> This bug is known and a patch has been submitted on 14 Jul 2003.
> http://sources.redhat.com/ml/ecos-patches/2003-07/msg00038.html (thanks
> to Scott Wilkinson ;-)).
> But, the eCos version I'm working on has been downloaded using CVS on
> september 2003 and the bugged file (rbtree.c) was not yet corrected.
It was committed 2003/01/22. Update your cvs tree.
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
next prev parent reply other threads:[~2003-11-21 9:57 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 [this message]
2003-11-21 10:09 ` David N. Welton
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=20031121095738.GE9114@lunn.ch \
--to=andrew@lunn.ch \
--cc=Vincent.Catros@elios-informatique.fr \
--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).