From: Gary Thomas <gary@mlbassoc.com>
To: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: [Fwd: RE: Possible deadlock in serial.c]
Date: Wed, 21 May 2003 17:03:00 -0000 [thread overview]
Message-ID: <1053536609.1558.563.camel@hermes> (raw)
[-- 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
next reply other threads:[~2003-05-21 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 17:03 Gary Thomas [this message]
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
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=1053536609.1558.563.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-maintainers@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).