From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: "Max Seidenstücker" <max.seidenstuecker@googlemail.com>
Cc: eCos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: PolarSSL for eCos
Date: Thu, 02 May 2013 14:55:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1305021748430.2039@sg-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1305021306380.2668@sg-laptop>
On Thu, 2 May 2013, Sergei Gavrikov wrote:
[snip]
> I knew that PolarSSL team became to provide FOSS License Exception
>
> https://polarssl.org/foss-license-exception
>
> IANAL, but it looks like that we would use GPL PolarSSL 2.0 with that
> FOSS exception in eCos. If this so, you would register new eCos project
[snip]
Please, read a warning from Paul Beskeen
http://ecos.sourceware.org/ml/ecos-maintainers/2013-05/msg00000.html
Sergei
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2013-05-02 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAASVbFEinhQ08pWw_MdtA+fk8EQ2suLOWMME3gxpG5M+KiHYsw@mail.gmail.com>
2013-05-02 11:14 ` Sergei Gavrikov
2013-05-02 14:55 ` 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.1305021748430.2039@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=max.seidenstuecker@googlemail.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).