From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: AnonCVS code freeze
Date: Wed, 04 Feb 2009 11:11:00 -0000 [thread overview]
Message-ID: <498977C6.2060203@eCosCentric.com> (raw)
In-Reply-To: <4976031F.3060307@eCosCentric.com>
Jonathan Larmour wrote:
> Dudes,
>
> I am starting the copyright header renaming. So that I don't have a moving
> target, I need to impose a code freeze. So please do not commit anything to
> anoncvs for the time being.
And is now (fully) unfrozen.
Jifl
--
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-04 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 17:00 Jonathan Larmour
2009-01-21 11:42 ` John Dallaway
2009-02-04 11:11 ` 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=498977C6.2060203@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
/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).