All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yanteng Si <siyanteng@loongson.cn>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	Alex Shi <alexs@kernel.org>
Subject: Re: [PATCH 1/6] docs: zh_CN: create the architecture-specific top-level directory
Date: Mon, 27 Mar 2023 09:19:10 +0800	[thread overview]
Message-ID: <92ec8165-90c4-366f-94de-d7ab731b4058@loongson.cn> (raw)
In-Reply-To: <20230323221948.352154-2-corbet@lwn.net>


在 3/24/23 06:19, Jonathan Corbet 写道:
> This mirrors commit 4f1bb0386dfc ("docs: create a top-level arch/
> directory"), creating a top-level directory to hold architecture-specific
> documentation.
>
> Cc: Alex Shi <alexs@kernel.org>
> Cc: Yanteng Si <siyanteng@loongson.cn>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Reviewed-by: Yanteng Si <siyanteng@loongson.cn>


Thanks,

Yanteng
> ---
>   .../translations/zh_CN/{arch.rst => arch/index.rst}  | 12 ++++++------
>   Documentation/translations/zh_CN/index.rst           |  2 +-
>   2 files changed, 7 insertions(+), 7 deletions(-)
>   rename Documentation/translations/zh_CN/{arch.rst => arch/index.rst} (72%)
>
> diff --git a/Documentation/translations/zh_CN/arch.rst b/Documentation/translations/zh_CN/arch/index.rst
> similarity index 72%
> rename from Documentation/translations/zh_CN/arch.rst
> rename to Documentation/translations/zh_CN/arch/index.rst
> index 690e173d8b2a..aa53dcff268e 100644
> --- a/Documentation/translations/zh_CN/arch.rst
> +++ b/Documentation/translations/zh_CN/arch/index.rst
> @@ -8,12 +8,12 @@
>   .. toctree::
>      :maxdepth: 2
>   
> -   mips/index
> -   arm64/index
> -   riscv/index
> -   openrisc/index
> -   parisc/index
> -   loongarch/index
> +   ../mips/index
> +   ../arm64/index
> +   ../riscv/index
> +   ../openrisc/index
> +   ../parisc/index
> +   ../loongarch/index
>   
>   TODOList:
>   
> diff --git a/Documentation/translations/zh_CN/index.rst b/Documentation/translations/zh_CN/index.rst
> index 7c3216845b71..299704c0818d 100644
> --- a/Documentation/translations/zh_CN/index.rst
> +++ b/Documentation/translations/zh_CN/index.rst
> @@ -120,7 +120,7 @@ TODOList:
>   .. toctree::
>      :maxdepth: 2
>   
> -   arch
> +   arch/index
>   
>   其他文档
>   --------


  parent reply	other threads:[~2023-03-27  1:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 22:19 [PATCH 0/6] Documentation: arch reorg (continued) Jonathan Corbet
2023-03-23 22:19 ` [PATCH 1/6] docs: zh_CN: create the architecture-specific top-level directory Jonathan Corbet
2023-03-24  7:16   ` Alex Shi
2023-03-27  1:19   ` Yanteng Si [this message]
2023-03-23 22:19 ` [PATCH 2/6] docs: move xtensa documentation under Documentation/arch/ Jonathan Corbet
2023-03-24  0:35   ` Max Filippov
2023-03-23 22:19 ` [PATCH 3/6] docs: move sparc " Jonathan Corbet
2023-03-23 22:19 ` [PATCH 4/6] docs: move superh " Jonathan Corbet
2023-03-23 22:19 ` [PATCH 5/6] docs: move openrisc " Jonathan Corbet
2023-03-24  1:43   ` Yanteng Si
2023-03-24  7:18     ` Alex Shi
2023-03-31 17:31   ` Stafford Horne
2023-03-23 22:19 ` [PATCH 6/6] docs: move nios2 " 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=92ec8165-90c4-366f-94de-d7ab731b4058@loongson.cn \
    --to=siyanteng@loongson.cn \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.