From: Weijie Yuan <wy@wyuan.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Wu XiangCheng <bobwxc@email.cn>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/zh_CN: update maintainer/configure-git.rst translation
Date: Mon, 24 Aug 2026 21:32:11 +0800 [thread overview]
Message-ID: <aoxH2xGlE_GY_Uyz@wyuan.org> (raw)
In-Reply-To: <87y0dv1wp3.fsf@trenco.lwn.net>
On Mon, Aug 24, 2026 at 07:20:56AM -0600, Jonathan Corbet wrote:
> Weijie Yuan <wy@wyuan.org> writes:
>
> > Upstream documented the common 'git tag -s' workflow and cleaned up
> > unneeded RST markup. It briefly updated the automatic lore Link: hook
> > for Git 2.41 and HTTPS, then removed that guidance because Link: tags
> > should only point to useful additional information.
> >
> > Add a SPDX-License-Identifier.
> >
> > Remove a useless top-of-file label, as Jon always tries to do.
> >
> > Update the translation through commit 944df7a31452
> > ("docs: update the guidance for Link: tags").
> >
> > Signed-off-by: Weijie Yuan <wy@wyuan.org>
> > ---
> > Hi Jon, I added a SPDX-License-Identifier for this file while the
> > original English one doesn't have one yet. Should I do that? / Is it
> > "legal" to do so? , if XiangCheng would be happy with what I'm doing.
>
> It's sort of an interesting case, actually.
>
> We don't know what license the original contributor intended, so it is
> hard to add an SPDX line to the original file. That contributor hasn't
> been seen in the community for a while, so it may or may not be easy to
> track him down and ask.
>
> A translation, though, is a derived product. Since everything in the
> kernel *can* be distributed under GPLv2, it is fair to say that your
> work is GPLv2, so the result of the translation effort must be too.
Yes, this is exactly what I'm thinking about.
> That said, I think it's better to stick with the original where
> possible.
OK, agreed. Will do that.
> Note, however, that I am *not* a lawyer, and that taking legal advice
> from me is probably a bad idea :)
Aha, yes. ;) Then I'd better be cautious.
Thanks!
prev parent reply other threads:[~2026-08-24 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 15:13 [PATCH] docs/zh_CN: update maintainer/configure-git.rst translation Weijie Yuan
2026-08-24 1:59 ` Alex Shi
2026-08-24 5:47 ` Weijie Yuan
2026-08-24 13:20 ` Jonathan Corbet
2026-08-24 13:32 ` Weijie Yuan [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=aoxH2xGlE_GY_Uyz@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.