This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Keeping 2.0 source tree up to date
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Grant Edwards <grante at visi dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: Mon, 22 Sep 2003 17:17:46 +0200
- Subject: Re: [ECOS] Keeping 2.0 source tree up to date
- References: <20030922094312.A14731@visi.com>
On Mon, Sep 22, 2003 at 09:43:18AM -0500, Grant Edwards wrote:
>
> Whats the recommended way to keep a 2.0 source tree up to date
> with bug fixes?
>
> Do I need to try to get BOFH to allow access to the CVS tree?
>
> Is there an official archive of approved patches somewhere that
> can be downloaded?
eCos does not use the linux model of a stable version and a
development version. 2.0 is static, will not change etc. All patches
are added to the head of the anoncvs tree. We try to keep that bug
free as possible, but there is always the risk that some patch will
break something. You can take a snapshot of the cvs, then run all the
test cases yourself in what ever configuration you need. If it passes,
its probably useable. If it fails, we would like to know!
If you want a certified release which has had extensive testing like
2.0 had, you need to contact the commercial support people.
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