From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: david@fromorbit.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 02/24] docs: carry a copy of the CC-by-SA 3.0 license
Date: Wed, 26 Sep 2018 14:30:28 -0700 [thread overview]
Message-ID: <20180926213028.GA22763@infradead.org> (raw)
In-Reply-To: <153799046767.31202.13234065186281153272.stgit@magnolia>
On Wed, Sep 26, 2018 at 12:34:27PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Add the CC-BY-SA 3.0 license so that the XFS Data Structures &
> Algorithms book can reference it with spdx headers.
NAK. We should not add random new licenses to the kernel tree.
next prev parent reply other threads:[~2018-09-27 3:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 19:34 [RFC PATCH 00/24] xfs-4.20: major documentation surgery Darrick J. Wong
2018-09-26 19:34 ` [PATCH 01/24] docs: convert xfs.txt to xfs.rst Darrick J. Wong
2018-09-26 19:34 ` [PATCH 02/24] docs: carry a copy of the CC-by-SA 3.0 license Darrick J. Wong
2018-09-26 21:30 ` Christoph Hellwig [this message]
2018-09-26 23:16 ` Darrick J. Wong
2018-09-26 23:21 ` Dave Chinner
2018-09-26 23:41 ` Darrick J. Wong
2018-09-26 19:34 ` [PATCH 03/24] docs: add skeleton of XFS Data Structures and Algorithms book Darrick J. Wong
2018-09-26 19:34 ` [PATCH 05/24] docs: add XFS self-describing metadata integrity doc to DS&A book Darrick J. Wong
2018-09-26 19:34 ` [PATCH 06/24] docs: add XFS delayed logging design " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 07/24] docs: add XFS shared data block chapter " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 08/24] docs: add XFS online repair " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 09/24] docs: add XFS common types and magic numbers " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 10/24] docs: add XFS testing chapter to the " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 11/24] docs: add XFS btrees " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 12/24] docs: add XFS dir/attr btree structure " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 13/24] docs: add XFS allocation group metadata " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 14/24] docs: add XFS reverse mapping structures " Darrick J. Wong
2018-09-26 19:35 ` [PATCH 15/24] docs: add XFS refcount btree structure to " Darrick J. Wong
2018-09-26 19:36 ` [PATCH 16/24] docs: add XFS log to the " Darrick J. Wong
2018-09-26 19:36 ` [PATCH 17/24] docs: add XFS internal inodes " Darrick J. Wong
2018-09-26 19:36 ` [PATCH 18/24] docs: add preliminary XFS realtime rmapbt structures " Darrick J. Wong
2018-09-26 19:36 ` [PATCH 19/24] docs: add XFS inode format " Darrick J. Wong
2018-09-26 19:36 ` [PATCH 20/24] docs: add XFS data extent map doc " Darrick J. Wong
2018-09-26 19:36 ` [PATCH 21/24] docs: add XFS directory structure " Darrick J. Wong
2018-09-26 19:36 ` [PATCH 22/24] docs: add XFS extended attributes structures " Darrick J. Wong
2018-09-26 19:37 ` [PATCH 23/24] docs: add XFS symlink " Darrick J. Wong
2018-09-26 19:37 ` [PATCH 24/24] docs: add XFS metadump structure to " Darrick J. Wong
2018-09-27 9:09 ` [RFC PATCH 00/24] xfs-4.20: major documentation surgery Carlos Maiolino
2018-09-27 14:50 ` Jonathan Corbet
2018-09-27 17:32 ` Darrick J. Wong
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=20180926213028.GA22763@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@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).