This is the mail archive of the
ecos-maintainers@sources.redhat.com
mailing list for the eCos project.
[Fwd: RE: Possible deadlock in serial.c]
- From: Gary Thomas <gary at mlbassoc dot com>
- To: eCos Maintainers <ecos-maintainers at sources dot redhat dot com>
- Date: 21 May 2003 11:03:29 -0600
- Subject: [Fwd: RE: Possible deadlock in serial.c]
- Organization: MLB Associates
So, what is the expected policy? I can't see any of us spending
tremendous resources trying to keep a release branch up-to-date.
Comments?
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--- Begin Message ---
- From: "David Marqvar (DAM)" <DAM at tt dot dk>
- To: 'Gary Thomas' <gary at mlbassoc dot com>
- Cc: eCos patches <ecos-patches at sources dot redhat dot com>
- Date: Wed, 21 May 2003 18:51:57 +0200
- Subject: RE: Possible deadlock in serial.c
> 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.
/David Marqvar
Thrane & Thrane
--- End Message ---