From: Jonathan Corbet <corbet@lwn.net>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] Documentation: xfs: Fix typo
Date: Fri, 7 Jun 2019 13:30:21 -0600 [thread overview]
Message-ID: <20190607133021.3a537e3a@lwn.net> (raw)
In-Reply-To: <20190607183410.GF1871505@magnolia>
On Fri, 7 Jun 2019 11:34:10 -0700
"Darrick J. Wong" <darrick.wong@oracle.com> wrote:
> I doubt the value of maintaining duplicate copies of this document in
> the kernel and the xfs documentation repo, and since the xfs docs and
> kernel licences aren't compatible maybe we should withdraw one...
Um .... the in-kernel docs say nothing about an incompatible license. I
see only a GPL license at the repo you pointed to as well. Is there
something I don't know going on here? If the licenses aren't compatible
then those files shouldn't be there.
Thanks,
jon
prev parent reply other threads:[~2019-06-07 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 3:05 [PATCH] Documentation: xfs: Fix typo Shiyang Ruan
2019-06-07 17:44 ` Jonathan Corbet
2019-06-07 18:34 ` Darrick J. Wong
2019-06-07 19:30 ` 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=20190607133021.3a537e3a@lwn.net \
--to=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ruansy.fnst@cn.fujitsu.com \
/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).