From: Jonathan Corbet <corbet@lwn.net>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Greg KH <greg@kroah.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: process: GPL -> GPL-compatible
Date: Fri, 1 Feb 2019 16:20:22 -0700 [thread overview]
Message-ID: <20190201162022.796ab977@lwn.net> (raw)
In-Reply-To: <20190122093408.16756-1-kilobyte@angband.pl>
On Tue, 22 Jan 2019 10:34:08 +0100
Adam Borowski <kilobyte@angband.pl> wrote:
> Drivers under MIT, BSD-17-clause, or uncle-Bob's-newest-take-on-PD are
> all fine, not just GPL.
>
> Signed-off-by: Adam Borowski <kilobyte@angband.pl>
> ---
> Not reformatting to fill lines, it'll semi-conflict with another patch
> that's been acked but not yet pushed.
It still conflicted (and the patch has indeed been pushed to docs-next).
I fixed it up and refilled the paragraph while I was at it.
Thanks,
jon
prev parent reply other threads:[~2019-02-01 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 9:34 [PATCH] doc: process: GPL -> GPL-compatible Adam Borowski
2019-01-22 10:23 ` Greg KH
2019-02-01 23:20 ` 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 \
--in-reply-to=20190201162022.796ab977@lwn.net \
--to=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=kilobyte@angband.pl \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).