From: Borislav Petkov <bp@alien8.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] LICENSES: Rename other to deprecated
Date: Tue, 14 May 2019 16:10:35 +0200 [thread overview]
Message-ID: <20190514141035.GC31140@zn.tnic> (raw)
In-Reply-To: <20190514134943.GA13662@lst.de>
On Tue, May 14, 2019 at 03:49:43PM +0200, Christoph Hellwig wrote:
> On Tue, May 14, 2019 at 12:26:32PM +0200, Borislav Petkov wrote:
> > This breaks scripts/spdxcheck.py, it needs below hunk. Also, should
> > "dual" be added to license_dirs too?
>
> Yes. In fact two people already submitted patches for that before
> you, just waiting for them to get picked up.
Yeah, it is definitely worth mentioning how minor stuff like that gets
noticed and fixed immediately in recent times. We've become better... :-)
Thx!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-05-14 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 10:51 clarify other licenses in LICENSES/ Christoph Hellwig
2019-04-30 10:51 ` [PATCH 1/3] docs: Don't reference the ZLib license in license-rules.rst Christoph Hellwig
2019-04-30 10:51 ` [PATCH 2/3] LICENSES: Clearly mark dual license only licenses Christoph Hellwig
2019-04-30 10:51 ` [PATCH 3/3] LICENSES: Rename other to deprecated Christoph Hellwig
2019-05-14 10:26 ` Borislav Petkov
2019-05-14 13:49 ` Christoph Hellwig
2019-05-14 14:10 ` Borislav Petkov [this message]
2019-04-30 11:41 ` clarify other licenses in LICENSES/ Greg Kroah-Hartman
2019-05-03 12:34 ` Jonathan Corbet
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=20190514141035.GC31140@zn.tnic \
--to=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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 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.