From: Samuel Bronson <naesten@gmail.com>
Cc: Achim Gratz <Achim.Gratz@Stromeko.DE>,
Yaakov Selkowitz <yselkowi@redhat.com>
Subject: License for clang patch "7.0.1-cygwin-driver.patch"
Date: Fri, 08 Apr 2022 18:22:01 -0400 [thread overview]
Message-ID: <87lewf43na.fsf@DESKTOP-5JD7O8D.localdomain> (raw)
The following message is a courtesy copy of an article
that has been posted to gmane.os.cygwin as well.
I was thinking of trying to upstream the patch at:
--text follows this line--
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/clang.git;a=blob;f=7.0.1-cygwin-driver.patch;h=8f2419846f3d649b81282868d8cd94de574a50f8;hb=e1fccf772aa5add40bba9050abeea188c62acbdd
But I expect the LLVM people would want to make sure that the changes
are licensed appropriately.
Unfortunately, I couldn't find anything about the licensing of the
packaging files in that packaging repository, nor do I see anything
about a licensing policy for packaging files on the page
<https://cygwin.com/packaging-contributors-guide.html>.
It doesn't exactly help that the LLVM project are in the midst of
relicensing their code, and the new policy only landed after the 8.x
branch, so even a "same as upstream code unless otherwise specified"
policy would only really help W.R.T. Achim Gratz's update of the patch
from clang 8.x to clang 9.x.
The current licensing policy for LLVM is described at:
<https://llvm.org/docs/DeveloperPolicy.html#copyright-license-and-patents>
Any ideas about this?
reply other threads:[~2022-04-11 0:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87lewf43na.fsf@DESKTOP-5JD7O8D.localdomain \
--to=naesten@gmail.com \
--cc=Achim.Gratz@Stromeko.DE \
--cc=yselkowi@redhat.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).