From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Paul Beskeen <paulb@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Fwd: [ECOS] Re: PolarSSL for eCos
Date: Thu, 02 May 2013 14:47:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1305021743310.2039@sg-laptop> (raw)
In-Reply-To: <5182626F.6090802@ecoscentric.com>
On Thu, 2 May 2013, Paul Beskeen wrote:
> Sergei and other maintainers,
>
> IANAL, but I don't think that the PolarSSL FOSS exception is that useful
> in the eCos context - eCos itself might be OK is my read - but certainly
> not any developer's proprietary embedded application that it is linked
> with. I think you should carefully consider the licensing aspects here
> before making this an official eCos project.
Paul, thank you for clarification, I understood your point (which I did
miss) I will make a references on this thread (your warning) on the eCos
discuss list.
Sergei
prev parent reply other threads:[~2013-05-02 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1305021306380.2668@sg-laptop>
2013-05-02 12:56 ` Paul Beskeen
2013-05-02 14:47 ` Sergei Gavrikov [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=alpine.DEB.2.00.1305021743310.2039@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=paulb@ecoscentric.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).