From: Christoph Hellwig <hch@infradead.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
Kai Germaschewski <kai.germaschewski@gmx.de>,
Masahiro Yamada <masahiroy@kernel.org>,
Marc Zyngier <maz@kernel.org>,
kernel@pengutronix.de, linux-spdx@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/2] SPDX tags for copyright
Date: Mon, 12 Sep 2022 22:05:54 -0700 [thread overview]
Message-ID: <YyAPsqKNSwdHccLj@infradead.org> (raw)
In-Reply-To: <20220908223850.13217-1-u.kleine-koenig@pengutronix.de>
On Fri, Sep 09, 2022 at 12:38:48AM +0200, Uwe Kleine-König wrote:
> Hello,
>
> for Debian packaging having SPDX license tags already simplifies
> creating the required copyright documentation considerably. Another
> information that is needed for Debian packaging is the copyright
> information. There is an SPDX way for copyright information, too. The
> second patch converts scripts/kallsyms.c to that mechanism as an example
> to maybe discuss if we want to do that in the kernel.
>
> While the SPDX-FileCopyrightText is officially a free-form field, I
> suggest to just stick to the format
>
> (<year> )?<copyright holder>
>
> to simplify machine consumption even further.
Adding the linux-spdx list and Linus. If we go with this format
(which doesn't sound bad), we'll clearly need to document the format
we want, and that people should use it.
next parent reply other threads:[~2022-09-13 5:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220908223850.13217-1-u.kleine-koenig@pengutronix.de>
2022-09-13 5:05 ` Christoph Hellwig [this message]
2022-09-13 8:20 ` [PATCH 0/2] SPDX tags for copyright Greg KH
2022-09-13 9:46 ` Uwe Kleine-König
2022-09-13 11:14 ` Greg KH
2022-09-13 13:12 ` Uwe Kleine-König
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=YyAPsqKNSwdHccLj@infradead.org \
--to=hch@infradead.org \
--cc=kai.germaschewski@gmx.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maz@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).