From: Jonathan Corbet <email@example.com> To: Thomas Gleixner <firstname.lastname@example.org>, Nishanth Menon <email@example.com>, Greg Kroah-Hartman <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org, Rahul T R <email@example.com>, Nishanth Menon <firstname.lastname@example.org> Subject: Re: [PATCH] scripts/spdxcheck.py: Lets strictly read license files in utf-8 Date: Wed, 07 Jul 2021 10:53:12 -0600 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Thomas Gleixner <email@example.com> writes: > Nishanth, > On Fri, Jul 02 2021 at 20:21, Nishanth Menon wrote: >> Commit bc41a7f36469 ("LICENSES: Add the CC-BY-4.0 license") >> unfortunately introduced LICENSES/dual/CC-BY-4.0 in UTF-8 Unicode text > > Sigh. Why are people adding such things w/o running this script in the > first place. I have a guess on that front ... there is nothing in our documentation that says anybody should run it, and the script itself gives no indication of what it does, when it should be run, or how to run it. That might just reduce uptake a little bit...:) I increasingly believe that anything we add to scripts/ should start with a "usage" header describing why it exists and how to make it do its thing. That would be a welcome addition to spdxcheck.py. Adding something to Documentation/process/license-rules.html would be a nice bonus. Thanks, jon
prev parent reply other threads:[~2021-07-07 16:53 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-03 1:21 Nishanth Menon 2021-07-07 9:00 ` Thomas Gleixner 2021-07-07 16:53 ` Jonathan Corbet [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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] scripts/spdxcheck.py: Lets strictly read license files in utf-8' \ /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
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).