From: Greg KH <gregkh@linuxfoundation.org>
To: Jules Octave <jbi.octave@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 1/2] staging: mt7621-dma: add SPDX GPL-2.0 or later version license identifier
Date: Fri, 1 Mar 2019 21:01:04 +0100 [thread overview]
Message-ID: <20190301200104.GA19353@kroah.com> (raw)
In-Reply-To: <CAOuULM6W1PtuaysLX7=z+nXhXnM35Wyz65Gx++urmrLJcbGe2w@mail.gmail.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Fri, Mar 01, 2019 at 05:38:58PM +0000, Jules Octave wrote:
> Some people say GPL-2.0+ has deprecated (
> https://www.drupal.org/project/lightning/issues/2938910 ) but I will
That is drupal, not the kernel.
> change it to GPL-2.0+.
> I tried looking on https://spdx.org/licenses/
That's a nice place to read as well, but we are using an "older" version
of spdx.
Always read the in-kernel documentation, we write it for a reason :)
Look at Documentation/process/license-rules.rst please, it shows that
you should use the "GPL-2.0+" marking.
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-01 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 15:17 [PATCH 0/2] staging: mt7621-dma: SPDX license cleanups Jules Irenge
2019-03-01 15:18 ` [PATCH 1/2] staging: mt7621-dma: add SPDX GPL-2.0 or later version license identifier Jules Irenge
2019-03-01 15:39 ` Greg KH
2019-03-01 17:38 ` Jules Octave
2019-03-01 20:01 ` Greg KH [this message]
2019-03-02 0:15 ` [Outreachy kernel] " Jules Octave
2019-03-02 6:30 ` Julia Lawall
2019-03-02 7:29 ` Jules Octave
2019-03-02 7:36 ` Julia Lawall
2019-03-01 15:18 ` [PATCH 2/2] staging: mt7621-dma: remove license boilerplate text Jules Irenge
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=20190301200104.GA19353@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jbi.octave@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.