From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: FSF switch
Date: Thu, 11 Sep 2003 12:31:00 -0000 [thread overview]
Message-ID: <3F606B15.5030708@eCosCentric.com> (raw)
In-Reply-To: <1063282679.18819.6573.camel@hermes>
Gary Thomas wrote:
> Jonathan,
>
> Any idea on the status of this move? It would sure be nice to get off
> the dime on this.
We're waiting on them at this stage, sorry. And as yet they are not
prepared to accept assignments in advance, so we can't just work on the
assumption either.
So, sorry! But I am actively discussing with them about it.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
prev parent reply other threads:[~2003-09-11 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 12:18 Gary Thomas
2003-09-11 12:31 ` 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=3F606B15.5030708@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.com \
--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).