From: Wolfgang Denk <wd@denx.de>
To: Gylstorff Quirin <quirin.gylstorff@siemens.com>
Cc: "Q. Gylstorff via Xenomai" <xenomai@xenomai.org>, Jan.kiszka@siemens.com
Subject: Re: [xenomai-images][PATCH 0/2] add xenomai 3.1.x to pipeline
Date: Fri, 18 Dec 2020 16:15:36 +0100 [thread overview]
Message-ID: <602475.1608304536@gemini.denx.de> (raw)
In-Reply-To: <2c1c5b9d-ebce-18e3-590e-2309d4306513@siemens.com>
Dear Quirin,
In message <2c1c5b9d-ebce-18e3-590e-2309d4306513@siemens.com> you wrote:
>
> > Is there a specific reason why all the new files come under a MIT
> > license, and not GPL ?
>
> I think you mix the two repositories 'xenomai-images' with 'xenomai' up.
Not really.
> The code in 'xenomai-images' was from the beginning MIT. The source code
> in the 'xenomai' repository is still GPL.
This des not answer my question. I asked _why_ this is MIT
licensed. I can see no good reason for not using GPL here, too ?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Summit meetings tend to be like panda matings. The expectations are
always high, and the results usually disappointing." - Robert Orben
next prev parent reply other threads:[~2020-12-18 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 9:49 [xenomai-images][PATCH 0/2] add xenomai 3.1.x to pipeline Q. Gylstorff
2020-12-18 9:49 ` [xenomai-images][PATCH 1/2] ci: add xenomai 3.1 stable Q. Gylstorff
2020-12-18 9:49 ` [xenomai-images][PATCH 2/2] ci: Introduce parent-child pipelines Q. Gylstorff
2020-12-18 13:22 ` [xenomai-images][PATCH 0/2] add xenomai 3.1.x to pipeline Wolfgang Denk
2020-12-18 14:48 ` Gylstorff Quirin
2020-12-18 15:15 ` Wolfgang Denk [this message]
2020-12-18 15:33 ` Jan Kiszka
2020-12-18 16:13 ` Wolfgang Denk
2020-12-18 16:36 ` Jan Kiszka
2021-01-07 17:46 ` Jan Kiszka
2021-01-07 19:03 ` Jan Kiszka
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=602475.1608304536@gemini.denx.de \
--to=wd@denx.de \
--cc=Jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.