mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Chen-Yu Yeh <chenyou910331@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	Yanteng Si <si.yanteng@linux.dev>,
	Hu Haowen <2023002089@link.tyut.edu.cn>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/16] docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst
Date: Wed, 22 Jul 2026 13:56:46 +0800	[thread overview]
Message-ID: <amBbnowQ9rvZ4rrx@wyuan.org> (raw)
In-Reply-To: <20260721215542.98435-2-chenyou910331@gmail.com>

On Wed, Jul 22, 2026 at 05:55:27AM +0800, Chen-Yu Yeh wrote:
>  使用Git管理補丁
>  ---------------
>  
> -內核使用分佈式版本控制始於2002年初,當時Linus首次開始使用專有的Bitkeeper應用
> -程序。雖然BitKeeper存在爭議,但它所體現的軟件版本管理方法卻肯定不是。分佈式
> -版本控制可以立即加速內核開發項目。現在有好幾種免費的BitKeeper替代品。
> -但無論好壞,內核項目都已經選擇了Git作爲其工具。
> +核心使用分散式版本控制始於2002年初,當時Linus首次開始使用專有的Bitkeeper應用
> +程式。雖然BitKeeper存在爭議,但它所體現的軟體版本管理方法卻肯定不是。分散式
> +版本控制可以立即加速核心開發專案。現在有好幾種免費的BitKeeper替代品。
> +但無論好壞,核心專案都已經選擇了Git作為其工具。

By the way, not about the actual diff here,

"免费的BitKeeper替代品" should be "自由的BitKeeper替代品"

The text above is about proprietary 专有的/專有的, so here should be
自由的.

zh_CN has this issus, too.

But this comment should not interfere with/block this patch. I suggest
fixing it with incremental patches later, for both.

Quoting GNU's article [1]

"Free software" means software that respects users' freedom and
community. Roughly, it means that the users have the freedom to run,
copy, distribute, study, change and improve the software. Thus, "free
software" is a matter of liberty, not price. To understand the concept,
you should think of "free" as in "free speech," not as in "free beer."
We sometimes call it "libre software," borrowing the French or Spanish
word for “free” as in freedom, to show we do not mean the software is
gratis.

[1] https://www.gnu.org/philosophy/free-sw.en.html

The rest of this patch seems good.

  reply	other threads:[~2026-07-22  5:57 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 21:55 [PATCH 00/16] docs/zh_TW: localize terminology and sync process/ documents Chen-Yu Yeh
2026-07-21 21:55 ` [PATCH 01/16] docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst Chen-Yu Yeh
2026-07-22  5:56   ` Weijie Yuan [this message]
2026-07-22  8:48   ` Weijie Yuan
2026-07-22 13:32     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 02/16] docs/zh_TW: process: localize terminology in 1.Intro.rst Chen-Yu Yeh
2026-07-22  7:42   ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 03/16] docs/zh_TW: process: localize terminology in code-of-conduct-interpretation.rst Chen-Yu Yeh
2026-07-21 21:55 ` [PATCH 04/16] docs/zh_TW: process: localize terminology in license-rules.rst Chen-Yu Yeh
2026-07-22 11:35   ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 05/16] docs/zh_TW: process: localize terminology in email-clients.rst Chen-Yu Yeh
2026-07-22 11:35   ` Weijie Yuan
2026-07-24  6:48     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 06/16] docs/zh_TW: process: localize terminology in programming-language.rst Chen-Yu Yeh
2026-07-22 14:51   ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 07/16] docs/zh_TW: process: localize terminology in coding-style.rst Chen-Yu Yeh
2026-07-22 14:48   ` Weijie Yuan
2026-07-24  6:38     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 08/16] docs/zh_TW: process: localize terminology in stable-kernel-rules.rst Chen-Yu Yeh
2026-07-21 21:55 ` [PATCH 09/16] docs/zh_TW: process: localize terminology in 5.Posting.rst Chen-Yu Yeh
2026-07-23  7:02   ` Weijie Yuan
2026-07-24  6:40     ` 葉宸佑
2026-07-24 14:11       ` Weijie Yuan
2026-07-25  0:46         ` 葉宸佑
2026-07-21 21:55 ` [PATCH 10/16] docs/zh_TW: process: localize terminology in 2.Process.rst Chen-Yu Yeh
2026-07-23  6:30   ` Weijie Yuan
2026-07-24  6:41     ` 葉宸佑
2026-07-24 13:57       ` Weijie Yuan
2026-07-26  8:56     ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 11/16] docs/zh_TW: process: localize terminology in howto.rst Chen-Yu Yeh
2026-07-23 10:53   ` Weijie Yuan
2026-07-24  6:41     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 12/16] docs/zh_TW: process: localize terminology in embargoed-hardware-issues.rst Chen-Yu Yeh
2026-07-23 12:43   ` Weijie Yuan
2026-07-24  6:42     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 13/16] docs/zh_TW: process: localize terminology in submitting-patches.rst Chen-Yu Yeh
2026-07-24 11:06   ` Weijie Yuan
2026-07-25  0:36     ` 葉宸佑
2026-08-05  7:00       ` Weijie Yuan
2026-07-21 21:55 ` [PATCH 14/16] docs/zh_TW: process: localize terminology in 8.Conclusion.rst Chen-Yu Yeh
2026-07-24 12:08   ` Weijie Yuan
2026-07-25  0:43     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 15/16] docs/zh_TW: process: localize terminology in index.rst Chen-Yu Yeh
2026-07-24 12:27   ` Weijie Yuan
2026-07-25  0:44     ` 葉宸佑
2026-07-21 21:55 ` [PATCH 16/16] docs/zh_TW: Add a glossary for Traditional Chinese translations Chen-Yu Yeh
2026-07-24 12:56   ` Weijie Yuan
2026-07-25  0:41     ` 葉宸佑
2026-07-22 15:09 ` [PATCH 00/16] docs/zh_TW: localize terminology and sync process/ documents Weijie Yuan
2026-07-24  6:36   ` 葉宸佑

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=amBbnowQ9rvZ4rrx@wyuan.org \
    --to=wy@wyuan.org \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=alexs@kernel.org \
    --cc=chenyou910331@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@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

Powered by JetHome