linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Rui Li <me@lirui.org>, Yanteng Si <siyanteng@loongson.cn>,
	Alex Shi <alexs@kernel.org>
Cc: Wu XiangCheng <wu.xiangcheng@linux.dev>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] docs/zh_CN: Add staging/xz Chinese translation
Date: Thu, 20 Oct 2022 08:04:57 -0600	[thread overview]
Message-ID: <87pmembng6.fsf@meer.lwn.net> (raw)
In-Reply-To: <63950114-5716-4de6-3c5f-1910c2c628be@lirui.org>

Rui Li <me@lirui.org> writes:

> Thanks for your reminding. I ran the check patch script before sending
> this patch.  However, the original file Documentation/staging/xz.rst
> seems not has SPDX-License-Identifier header.

You cannot know what the license of the source file is, since it hasn't
been declared there.  What you *do* know, though, is that it must be
GPLv2 compatible.  Your translation can thus be strictly GPLv2.  My
suggestion in such cases would be to put:

.. SPDX-License-Identifier: GPL-2.0

into translations of documents that lack an SPDX line of their own.

Thanks,

jon

  reply	other threads:[~2022-10-20 14:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 12:11 [PATCH v2 0/2] docs/zh_CN: Add staging/index and xz Chinese translation Rui Li
2022-10-19 12:11 ` [PATCH v2 1/2] docs/zh_CN: Add staging/index " Rui Li
2022-10-20  6:52   ` Yanteng Si
2022-10-19 12:11 ` [PATCH v2 2/2] docs/zh_CN: Add staging/xz " Rui Li
2022-10-20  6:53   ` Yanteng Si
2022-10-20  9:24   ` Yanteng Si
2022-10-20  9:31     ` Rui Li
2022-10-20 14:04       ` Jonathan Corbet [this message]
2022-10-20 14:17         ` Rui Li

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=87pmembng6.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexs@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@lirui.org \
    --cc=siyanteng@loongson.cn \
    --cc=wu.xiangcheng@linux.dev \
    /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).