From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: FSF assignment status
Date: Mon, 04 Aug 2003 14:32:00 -0000 [thread overview]
Message-ID: <3F2E6E8B.5010501@eCosCentric.com> (raw)
In-Reply-To: <20030804094121.GA1771@biferten.ma.tech.ascom.ch>
Andrew Lunn wrote:
> Hi Folks
>
> I see that Nick has put a draft FSF assignment document into CVS.
>
> What is the status? What is the best guess for swapping to FSF?
There's a few things we to need to ask them that cropped up, so I'd guess
not this week... maybe a couple of weeks.
Obviously then we'll honour our gentleman's agreement and assign all our
code to the FSF.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next prev parent reply other threads:[~2003-08-04 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 9:41 Andrew Lunn
2003-08-04 14:32 ` Jonathan Larmour [this message]
2003-08-04 14:35 ` Nick Garnett
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=3F2E6E8B.5010501@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--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).