From: John Dallaway <jld@ecoscentric.com>
To: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: ecos-v2_0-branch [ was Re: [Fwd: RE: Possible deadlock in serial.c] ]
Date: Wed, 21 May 2003 19:01:00 -0000 [thread overview]
Message-ID: <200305212001.44191.jld@ecoscentric.com> (raw)
In-Reply-To: <3ECBBF6A.5080508@eCosCentric.com>
I think the finite time we can devote to "eCos maintainer" activities is
better spent on improving the head (including the processing of contributed
patches) than maintaining a release branch which has now fulfilled its
purpose. I therefore propose that we consider the ecos-v2_0-branch to be
dead.
John Dallaway
-----Original Message-----
From: Jonathan Larmour
Date: Wednesday 21 May 2003 19:03
Subject: Re: [Fwd: RE: Possible deadlock in serial.c]
> Gary Thomas wrote:
> > 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?
>
> The branch is tagged with a release tag, so I have no aversion if people
> _want_ to check fixes in.... but my personal opinion is that I can't see
> us doing another release based on the 2.0 branch. If we wanted to do one,
> I would suggest cutting a new branch off the trunk. But there's nothing
> to warrant that for a while yet IMHO.
>
> BTW, sorry I've been well out of the loop recently. I'm still, er,
> preoccupied (as per <http://worf.jifvik.org:9999/gallery/baby>). I'll try
> and get back into things now.
>
> Jifl
next prev parent reply other threads:[~2003-05-21 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` John Dallaway [this message]
2003-05-21 19:04 ` ecos-v2_0-branch [ was Re: [Fwd: RE: Possible deadlock in serial.c] ] 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=200305212001.44191.jld@ecoscentric.com \
--to=jld@ecoscentric.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).