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: Mon, 27 Apr 2020 13:38:58 -0700 [thread overview]
Message-ID: <fdcc8aa5a506ba9c6a3e6e68a7147161424985bf.camel@perches.com> (raw)
In-Reply-To: <CAHk-=wgN=Ox112_O=GQ-kwMxYduix9gZFsr1GXXJWLpDpNDm5g@mail.gmail.com>
On Mon, 2020-04-27 at 12:40 -0700, Linus Torvalds wrote:
> On Mon, Apr 27, 2020 at 11:59 AM Joe Perches <joe@perches.com> wrote:
> > There's no real reason not to prefer the latest versions
> > over the deprecated ones.
>
> Joe, your pedantic approach is really hard to work with. Please work on it.
License text especially _should_ be pedantic and precise.
> The fact is, there *is * a reason to avoid the pedantic "change to new
> version" - pointless churn.
Have you *looked* at this proposed change?
It just changes // SPDX comments to /* */ in .h files.
It's generically useless churn as using the // style in .h files
was only for old and now unsupported compiler versions.
> We have a lot of the original style spdx markers, because those are
> what we started with. And changing them is pointless.
You and I (and apparently the SPDX group too as they deprecated it)
disagree a bit here.
> I know you love your scripts to change things around, but to everybody
> else it tends to be just extra work and noise.
Piecemeal changes aren't great.
Scripted changes can be very useful and I believe they
are significantly underutilized in this source tree.
cheers, Joe
next prev parent reply other threads:[~2020-04-27 20:39 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 [this message]
2020-04-27 20:46 ` Linus Torvalds
2020-04-29 0:20 ` Joe Perches
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=fdcc8aa5a506ba9c6a3e6e68a7147161424985bf.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®