From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: eCos 3.0 updates
Date: Tue, 24 Feb 2009 17:12:00 -0000 [thread overview]
Message-ID: <49A42A5B.3070604@eCosCentric.com> (raw)
In-Reply-To: <49A42927.4030800@mlbassoc.com>
Gary Thomas wrote:
> Jonathan Larmour wrote:
>> Gary Thomas wrote:
>>> I assume that checkin/updates for this go on the ecos-v3_0-branch?
>> Yes but primarily for fixes only. Anything more major should probably be
>> double-checked on this list. See mail from jld of 2009-02-22 09:17:
>>
>> "The ecos-v3_0-branch is now tagged and unfrozen. However, please limit
>> changes on this branch to patches which directly address issues in the
>> eCos 3.0 beta 1 release.
>>
>> It would be helpful to ensure that a Bugzilla issue is raised (version
>> == "3.0beta1") for each patch so we can readily review what has been
>> fixed and what is outstanding."
>
> Fair enough; I was going to commit a change for BZ #1000672
>
> I assume that whatever goes in on this branch eventually gets
> merged to the trunk?
Nope, I don't think there's any plan to do that - please double-commit to
both instead.
Jifl
--
*See us at Embedded World 2009, Nürnberg, Germany, 3-5 Mar, Stand 11-300*
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
prev parent reply other threads:[~2009-02-24 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 16:31 Gary Thomas
2009-02-24 16:59 ` Jonathan Larmour
2009-02-24 17:07 ` Gary Thomas
2009-02-24 17:12 ` Jonathan Larmour [this message]
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=49A42A5B.3070604@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=gary@mlbassoc.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).