From: Wolfgang Denk <wd@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Q. Gylstorff" <Quirin.Gylstorff@siemens.com>,
"Q. Gylstorff via Xenomai" <xenomai@xenomai.org>
Subject: Re: [xenomai-images][PATCH 0/2] add xenomai 3.1.x to pipeline
Date: Fri, 18 Dec 2020 17:13:17 +0100 [thread overview]
Message-ID: <603946.1608307997@gemini.denx.de> (raw)
In-Reply-To: <e6cb9740-b142-d84a-84b5-1098887c03cb@siemens.com>
Dear Jan,
In message <e6cb9740-b142-d84a-84b5-1098887c03cb@siemens.com> you wrote:
>
> >> Add xenomai 3.1 to the build and test pipeline of xenomai-images.
> >
> > Is there a specific reason why all the new files come under a MIT
> > license, and not GPL ?
>
> Yes, these are bitbake recipes, derived from Isar recipes. We follow
> that practice in all related projects.
I wonder why I can't just get a clear answer?
I did not ask _what_ you do - that I see. I asked _why_ you are
doing it? What is the rationale for chosing MIT instead of for
example GPL?
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
Always try to do things in chronological order; it's less confusing
that way.
next prev parent reply other threads:[~2020-12-18 16:13 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
2020-12-18 15:33 ` Jan Kiszka
2020-12-18 16:13 ` Wolfgang Denk [this message]
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=603946.1608307997@gemini.denx.de \
--to=wd@denx.de \
--cc=Quirin.Gylstorff@siemens.com \
--cc=jan.kiszka@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.