From: Christoph Hellwig <hch@infradead.org>
To: Richard Fontana <rfontana@redhat.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
J Lovejoy <opensource@jilayne.com>,
linux-spdx@vger.kernel.org
Subject: Re: some ideas on guidelines
Date: Sun, 18 Aug 2019 21:30:43 -0700 [thread overview]
Message-ID: <20190819043043.GA14746@infradead.org> (raw)
In-Reply-To: <CAC1cPGwDOeeFN5EmZjhT_Ge+95i=thgKAP_kjJiEKc_KciMftw@mail.gmail.com>
I know a project that reuses a lot of kernel code (xfsprogs), and we
are perfectly fine with GPLv2 only, and we have a few others that
are pretty similar.
next prev parent reply other threads:[~2019-08-19 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 5:25 some ideas on guidelines J Lovejoy
2019-06-12 10:26 ` Philippe Ombredanne
2019-06-24 0:57 ` J Lovejoy
2019-06-12 16:04 ` John Sullivan
2019-06-24 1:01 ` J Lovejoy
2019-06-13 17:44 ` Richard Fontana
2019-06-14 14:25 ` Richard Fontana
2019-06-17 4:44 ` J Lovejoy
2019-06-24 1:08 ` J Lovejoy
2019-08-17 19:55 ` J Lovejoy
2019-08-18 5:08 ` Greg KH
2019-08-18 22:08 ` Richard Fontana
2019-08-19 4:30 ` Christoph Hellwig [this message]
2019-08-19 5:06 ` Greg KH
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=20190819043043.GA14746@infradead.org \
--to=hch@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-spdx@vger.kernel.org \
--cc=opensource@jilayne.com \
--cc=rfontana@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 NNTP newsgroup(s).