From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] misc: remove COPYING from doc/ Makefile
Date: Tue, 31 Jul 2018 00:43:13 -0700 [thread overview]
Message-ID: <20180731074313.GA19990@infradead.org> (raw)
In-Reply-To: <e4d64c9b-5a1a-54b5-8b69-463738c95307@redhat.com>
On Mon, Jul 30, 2018 at 10:41:54PM -0500, Eric Sandeen wrote:
> COPYING is gone now, so make doc-install breaks.
>
> Fixes: 959ef98 ("xfsprogs: convert to SPDX license tags")
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
The patch itself looks good, but I think we have a deeper problem,
in that there is no actual license information anywhere in xfsprogs now.
We need to fix that up similar to the LICENSES/ directory in the kernel.
SPDX tags are good and nice, but without an explanation what they mean
in the same source tree they are useless.
next prev parent reply other threads:[~2018-07-31 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 3:41 [PATCH] misc: remove COPYING from doc/ Makefile Eric Sandeen
2018-07-31 3:45 ` Darrick J. Wong
2018-07-31 7:43 ` Christoph Hellwig [this message]
2018-07-31 8:06 ` Dave Chinner
2018-07-31 8:08 ` Christoph Hellwig
2018-07-31 15:36 ` Eric Sandeen
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=20180731074313.GA19990@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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).