linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bernhard+linux-doc@lsmod.de
To: linux-doc@vger.kernel.org
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>,
	Bernard Zhao <bernard@vivo.com>, Jonathan Corbet <corbet@lwn.net>,
	"Bernhard M. Wiedemann" <bwiedemann@suse.de>
Subject: [PATCH] docs/zh_TW+zh_CN: Make rst references unique
Date: Fri, 20 Sep 2024 09:01:44 +0200	[thread overview]
Message-ID: <20240920070144.26947-1-bernhard+linux-doc@lsmod.de> (raw)
In-Reply-To: <20240905113531.65375-1-bernhard+linux-doc@lsmod.de>

From: "Bernhard M. Wiedemann" <bwiedemann@suse.de>

We found that sphinx parallel processing would randomly pick
one or the other
https://github.com/sphinx-doc/sphinx/issues/6714#issuecomment-2362212754

Signed-off-by: Bernhard M. Wiedemann <bwiedemann@suse.de>
---
 Documentation/translations/zh_CN/dev-tools/gcov.rst | 8 ++++----
 Documentation/translations/zh_TW/dev-tools/gcov.rst | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/Documentation/translations/zh_CN/dev-tools/gcov.rst b/Documentation/translations/zh_CN/dev-tools/gcov.rst
index 3158c9da1318..ea8f94852f41 100644
--- a/Documentation/translations/zh_CN/dev-tools/gcov.rst
+++ b/Documentation/translations/zh_CN/dev-tools/gcov.rst
@@ -120,7 +120,7 @@ gcov的内核分析插桩支持内核的编译和运行是在同一台机器上
 如果内核编译和运行是不同的机器,那么需要额外的准备工作,这取决于gcov工具
 是在哪里使用的:
 
-.. _gcov-test_zh:
+.. _gcov-test_zh_CN:
 
 a) 若gcov运行在测试机上
 
@@ -140,7 +140,7 @@ a) 若gcov运行在测试机上
     如果文件是软链接,需要替换成真正的目录文件(这是由make的当前工作
     目录变量CURDIR引起的)。
 
-.. _gcov-build_zh:
+.. _gcov-build_zh_CN:
 
 b) 若gcov运行在编译机上
 
@@ -205,7 +205,7 @@ kconfig会根据编译工具链的检查自动选择合适的gcov格式。
 --------------------------
 
 用于在编译机上收集覆盖率元文件的示例脚本
-(见 :ref:`编译机和测试机分离 a. <gcov-test_zh>` )
+(见 :ref:`编译机和测试机分离 a. <gcov-test_zh_CN>` )
 
 .. code-block:: sh
 
@@ -238,7 +238,7 @@ kconfig会根据编译工具链的检查自动选择合适的gcov格式。
 -------------------------
 
 用于在测试机上收集覆盖率数据文件的示例脚本
-(见 :ref:`编译机和测试机分离 b. <gcov-build_zh>` )
+(见 :ref:`编译机和测试机分离 b. <gcov-build_zh_CN>` )
 
 .. code-block:: sh
 
diff --git a/Documentation/translations/zh_TW/dev-tools/gcov.rst b/Documentation/translations/zh_TW/dev-tools/gcov.rst
index ce1c9a97de16..39ac3fff44cd 100644
--- a/Documentation/translations/zh_TW/dev-tools/gcov.rst
+++ b/Documentation/translations/zh_TW/dev-tools/gcov.rst
@@ -120,7 +120,7 @@ gcov的內核分析插樁支持內核的編譯和運行是在同一臺機器上
 如果內核編譯和運行是不同的機器,那麼需要額外的準備工作,這取決於gcov工具
 是在哪裏使用的:
 
-.. _gcov-test_zh:
+.. _gcov-test_zh_TW:
 
 a) 若gcov運行在測試機上
 
@@ -140,7 +140,7 @@ a) 若gcov運行在測試機上
     如果文件是軟鏈接,需要替換成真正的目錄文件(這是由make的當前工作
     目錄變量CURDIR引起的)。
 
-.. _gcov-build_zh:
+.. _gcov-build_zh_TW:
 
 b) 若gcov運行在編譯機上
 
@@ -205,7 +205,7 @@ kconfig會根據編譯工具鏈的檢查自動選擇合適的gcov格式。
 --------------------------
 
 用於在編譯機上收集覆蓋率元文件的示例腳本
-(見 :ref:`編譯機和測試機分離 a. <gcov-test_zh>` )
+(見 :ref:`編譯機和測試機分離 a. <gcov-test_zh_TW>` )
 
 .. code-block:: sh
 
@@ -238,7 +238,7 @@ kconfig會根據編譯工具鏈的檢查自動選擇合適的gcov格式。
 -------------------------
 
 用於在測試機上收集覆蓋率數據文件的示例腳本
-(見 :ref:`編譯機和測試機分離 b. <gcov-build_zh>` )
+(見 :ref:`編譯機和測試機分離 b. <gcov-build_zh_TW>` )
 
 .. code-block:: sh
 
-- 
2.35.3

  parent reply	other threads:[~2024-09-20  7:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 11:35 [PATCH] docs: Build kernel docs deterministically bernhard+linux-doc
2024-09-05 12:04 ` Jani Nikula
2024-09-05 12:20   ` Jani Nikula
2024-09-05 13:29     ` Vegard Nossum
2024-09-05 14:08       ` Jani Nikula
2024-09-05 14:50         ` Vegard Nossum
2024-09-05 12:57   ` Bernhard M. Wiedemann
2024-09-05 13:07     ` Jani Nikula
2024-09-05 18:01       ` Jonathan Corbet
2024-09-05 18:38         ` Jani Nikula
2024-09-05 19:19           ` Jani Nikula
2024-09-06 13:43         ` Bernhard M. Wiedemann
2024-09-06  9:11 ` Vegard Nossum
2024-09-06 13:56   ` Bernhard M. Wiedemann
2024-09-06 14:53     ` Akira Yokosawa
2024-09-20  7:01 ` bernhard+linux-doc [this message]
2024-09-23  5:36   ` [PATCH] docs/zh_TW+zh_CN: Make rst references unique Yanteng Si
2024-10-07 17:23   ` Jonathan Corbet

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=20240920070144.26947-1-bernhard+linux-doc@lsmod.de \
    --to=bernhard+linux-doc@lsmod.de \
    --cc=alexs@kernel.org \
    --cc=bernard@vivo.com \
    --cc=bwiedemann@suse.de \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=siyanteng@loongson.cn \
    /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).