From: Gary Thomas <gary@mlbassoc.com>
To: "Austin, Brian" <Brian.Austin@cirrus.com>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Cirrus contribution
Date: Thu, 16 Apr 2009 14:53:00 -0000 [thread overview]
Message-ID: <49E74644.9050302@mlbassoc.com> (raw)
In-Reply-To: <C171323BB93CB94897E300CBB6D4537F17D805A2@CLMSG-01.ad.cirrus.com>
Austin, Brian wrote:
> I need some more info on why Cirrus has to sign over the "rights" to the
> code. This is a stickler for our legal, and they are concerned as to why
> we have to sign something. I know, I know, but if there is any
> documentation as to why we have to do this, it would help me a great
> deal. I'm still working with our legal department, and I think I can
> get it done, but would like more ammo is yall have anything else for me
> to help the cause.....
Look at the FSF documents/website. The FSF is the copyright holder
for all of eCos. Anything which is to be added or significantly changed
must relinquish all copyright claims to the FSF.
> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com]
> Sent: Friday, April 10, 2009 10:33 AM
> To: Austin, Brian
> Cc: eCos Maintainers
> Subject: Cirrus contribution
>
> Brian,
>
> Thanks for posting this. We (I for sure) will be looking
> at this soon, awaiting your formal assignment to the FSF.
>
> Thanks again
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2009-04-16 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 15:32 Gary Thomas
2009-04-10 15:34 ` Austin, Brian
2009-04-16 14:45 ` Austin, Brian
2009-04-16 14:53 ` Gary Thomas [this message]
2009-04-16 16:10 ` John Dallaway
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=49E74644.9050302@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=Brian.Austin@cirrus.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).