All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <seakeel@gmail.com>
To: Weijie Yuan <wy@wyuan.org>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <si.yanteng@linux.dev>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Wu XiangCheng <bobwxc@email.cn>
Cc: 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 09:59:47 +0800	[thread overview]
Message-ID: <6c674f81-35ca-4074-b22a-b9ed6122ce6c@gmail.com> (raw)
In-Reply-To: <20260823-configure-git-v1-1-3c65eefcc585@wyuan.org>



On 2026/8/23 23:13, Weijie Yuan wrote:
> 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.
> 

I am not Jon. but usually changes should start from the original file. 
we don't add or change anything different from it.

Thanks!

  reply	other threads:[~2026-08-24  1:59 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 [this message]
2026-08-24  5:47   ` Weijie Yuan
2026-08-24 13:20 ` Jonathan Corbet
2026-08-24 13:32   ` Weijie Yuan

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=6c674f81-35ca-4074-b22a-b9ed6122ce6c@gmail.com \
    --to=seakeel@gmail.com \
    --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 \
    --cc=wy@wyuan.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.