From: FSF General Contact Address <info@fsf.org>
To: ecos-maintainers@sources.redhat.com
Subject: Re: [gnu.org #25869] eCos as an FSF project?
Date: Mon, 19 May 2003 22:20:00 -0000 [thread overview]
Message-ID: <20030519210746.GR1403@gnu.org> (raw)
Dear eCos team,
About a month ago, you wrote to us with interest in becoming part of the
GNU project, and questions about what would be necessary to do so. I have
not heard from you since. If you could just let me know what has come of
this so far -- if you've come to a decision one way or the other, have
further questions, are still considering the issue, or whatever else -- I
would appreciate a quick note.
If it is of any help, I would like to point out that we would be happy to
help negotiate copyright and licensing issues with Red Hat, particularly on
the documentation, if we are able to obtain copyright on the software.
Also, if you have not yet made a decision, I would appreciate if you could
answer a quick question of ours. We were wondering if people use GNU
software with eCos -- have a GNU/eCos system, in other words -- and if so,
how common it is to use GNU software with eCos. Any examples of such
systems you could refer us to would be helpful as well.
I look forward to hearing back from you soon.
Best regards,
--
Brett Smith, Free Software Foundation
Become a card-carrying member of FSF:
http://member.fsf.org/
Help support our work for FSF and the GNU project:
http://svcs.affero.net/rm.php?r=fsfinfo
next reply other threads:[~2003-05-19 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 22:20 FSF General Contact Address [this message]
2003-05-19 22:56 ` Jonathan Larmour
[not found] <rt-25869@gnu.org>
[not found] ` <rt-25869-69834.13.1459854406747@rt.gnu.org>
2003-03-28 19:57 ` FSF General Contact Address
2003-04-03 19:51 ` Jonathan Larmour
[not found] ` <rt-25869-73954.4.22037571649483@rt.gnu.org>
2003-04-10 22:08 ` FSF General Contact Address
2003-04-10 23:21 ` Jonathan Larmour
2003-04-11 7:50 ` Andrew Lunn
2003-04-11 12:02 ` Nick Garnett
2003-04-13 18:20 ` Bart Veer
2003-04-14 19:50 ` Jonathan Larmour
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=20030519210746.GR1403@gnu.org \
--to=info@fsf.org \
--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).