This is the mail archive of the
ecos-patches@sources.redhat.com
mailing list for the eCos project.
RE: Possible deadlock in serial.c
- From: Gary Thomas <gary at mlbassoc dot com>
- To: "David Marqvar (DAM)" <DAM at tt dot dk>
- Cc: eCos patches <ecos-patches at sources dot redhat dot com>
- Date: 21 May 2003 12:52:30 -0600
- Subject: RE: Possible deadlock in serial.c
- Organization: MLB Associates
- References: <E70B4FA554FB6C44BC7FAC9A9CE0CBC436D53B@ntex.tt.dk>
On Wed, 2003-05-21 at 10:51, David Marqvar (DAM) wrote:
> > This looks reasonable to me and I have applied the change (patch
> > attached).
> Good :-)
>
> > I don't think that there will be any patches made to the 2.0 branch
> > now that it has been "released".
>
> Does that mean that the ecos-v2_0-branch will *not* be touched at all from
> now on?
> It comes as a surprise to me since I would expect bug-fixes with relevance
> for eCos 2.0 to be committed to this branch as well - thus only new
> features/major revisions would be kept solely in the latest branch.
>
If there are really serious bugs that can be fixed on that branch, it
may happen. I don't expect it though - we [as mostly volunteers] don't
have the resources to keep the branch up to date, nor do we expect to
ever have a follow-on release from the branch.
The trunk is kept quite stable and has many improvements already that
aren't in the 2.0 release. Is there something that keeps you from
using it?
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates