From: Min-Hua Chen <minhuadotchen@gmail.com>
To: Hu Haowen <src.res@email.cn>, Jonathan Corbet <corbet@lwn.net>
Cc: Min-Hua Chen <minhuadotchen@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc-tw-discuss@lists.sourceforge.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] docs: sparse: move TW sparse.txt to TW dev-tools
Date: Fri, 11 Aug 2023 23:35:53 +0800 [thread overview]
Message-ID: <20230811153554.84571-2-minhuadotchen@gmail.com> (raw)
In-Reply-To: <20230811153554.84571-1-minhuadotchen@gmail.com>
Follow Randy's advice [1] to move
Documentation/translations/zh_TW/sparse.txt
to
Documentation/translations/zh_TW/dev-tools/sparse.txt
[1] https://lore.kernel.org/lkml/bfab7c5b-e4d3-d8d9-afab-f43c0cdf26cf@infradead.org/
Cc: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Min-Hua Chen <minhuadotchen@gmail.com>
---
Documentation/translations/zh_TW/{ => dev-tools}/sparse.txt | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Documentation/translations/zh_TW/{ => dev-tools}/sparse.txt (100%)
diff --git a/Documentation/translations/zh_TW/sparse.txt b/Documentation/translations/zh_TW/dev-tools/sparse.txt
similarity index 100%
rename from Documentation/translations/zh_TW/sparse.txt
rename to Documentation/translations/zh_TW/dev-tools/sparse.txt
--
2.34.1
next parent reply other threads:[~2023-08-11 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230811153554.84571-1-minhuadotchen@gmail.com>
2023-08-11 15:35 ` Min-Hua Chen [this message]
2023-08-11 17:02 ` [PATCH 1/2] docs: sparse: move TW sparse.txt to TW dev-tools Randy Dunlap
2023-08-11 15:35 ` [PATCH 2/2] docs: sparse: convert TW sparse.txt into sparse.rst Min-Hua Chen
2023-08-11 17:02 ` Randy Dunlap
2023-08-11 20:41 ` Jonathan Corbet
2023-08-12 0:37 ` Min-Hua Chen
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=20230811153554.84571-2-minhuadotchen@gmail.com \
--to=minhuadotchen@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc-tw-discuss@lists.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=src.res@email.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).