From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
"Kate Stewart" <kstewart@linuxfoundation.org>,
"Nishad Kamdar" <nishadkamdar@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
linux-xfs <linux-xfs@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfs: Use the correct style for SPDX License Identifier
Date: Tue, 28 Apr 2020 17:20:47 -0700 [thread overview]
Message-ID: <08eafcec5b92626e1ad7906b948419e7300e7684.camel@perches.com> (raw)
In-Reply-To: <CAHk-=wi2bdXuYhC9bd9FShtcf_u-6RUb3Qr_aXq3XtbCxR5NGQ@mail.gmail.com>
On Mon, 2020-04-27 at 13:46 -0700, Linus Torvalds wrote:
> There is simply no point in EVER changing "GPL-2.0" into
> "GPL-2.0-only" etc, unless the thing is then touched for some other
> reason (which it may never be).
Which is _exactly_ what is happening here.
But the reason _not_ to touch it here is there would
be a difference between the SPDX license text in the
.c and .h files in the directory.
prev parent reply other threads:[~2020-04-29 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 13:35 Nishad Kamdar
2020-04-27 7:25 ` Christoph Hellwig
2020-05-02 8:57 ` Nishad Kamdar
2020-04-27 15:56 ` Darrick J. Wong
2020-04-27 17:29 ` Greg Kroah-Hartman
2020-04-27 17:41 ` Joe Perches
2020-04-27 17:46 ` Greg Kroah-Hartman
2020-04-27 18:01 ` Joe Perches
2020-04-27 18:36 ` Greg Kroah-Hartman
2020-04-27 18:59 ` Joe Perches
2020-04-27 19:40 ` Linus Torvalds
2020-04-27 20:38 ` Joe Perches
2020-04-27 20:46 ` Linus Torvalds
2020-04-29 0:20 ` Joe Perches [this message]
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=08eafcec5b92626e1ad7906b948419e7300e7684.camel@perches.com \
--to=joe@perches.com \
--cc=darrick.wong@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nishadkamdar@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.de \
/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
all inboxes | Powered by JetHome®