public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
* [Fwd: RE: Possible deadlock in serial.c]
@ 2003-05-21 17:03 Gary Thomas
  2003-05-21 18:04 ` Jonathan Larmour
  0 siblings, 1 reply; 4+ messages in thread
From: Gary Thomas @ 2003-05-21 17:03 UTC (permalink / raw)
  To: eCos Maintainers

[-- Attachment #1: Type: text/plain, Size: 193 bytes --]

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

[-- Attachment #2: Forwarded message - RE: Possible deadlock in serial.c --]
[-- Type: message/rfc822, Size: 2094 bytes --]

From: "David Marqvar (DAM)" <DAM@tt.dk>
To: 'Gary Thomas' <gary@mlbassoc.com>
Cc: eCos patches <ecos-patches@sources.redhat.com>
Subject: RE: Possible deadlock in serial.c
Date: Wed, 21 May 2003 18:51:57 +0200
Message-ID: <E70B4FA554FB6C44BC7FAC9A9CE0CBC436D53B@ntex.tt.dk>

> 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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2003-05-21 19:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-21 17:03 [Fwd: RE: Possible deadlock in serial.c] Gary Thomas
2003-05-21 18:04 ` Jonathan Larmour
2003-05-21 19:01   ` ecos-v2_0-branch [ was Re: [Fwd: RE: Possible deadlock in serial.c] ] John Dallaway
2003-05-21 19:04     ` Gary Thomas

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).