From: Alex Shi <seakeel@gmail.com>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
"Wu X.C." <bobwxc@email.cn>, Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
yanteng si <siyanteng01@gmail.com>,
zhoubinbin@loongson.cn
Subject: Re: [PATCH v2 3/3] docs/zh_CN: Update the translation of vm index to 5.19-rc1
Date: Tue, 14 Jun 2022 21:42:46 +0800 [thread overview]
Message-ID: <CAJy-AmkAHT80n7BUfCi0kj4zMZYtUdG7q=WrUnnkUbg_mVZ4_g@mail.gmail.com> (raw)
In-Reply-To: <4d48992c-b09d-3a56-19d5-23b5f971cbcd@loongson.cn>
On Tue, Jun 14, 2022 at 9:02 PM Yanteng Si <siyanteng@loongson.cn> wrote:
>
> On 2022/6/13 下午2:30, Alex Shi wrote:
> > On Mon, Jun 13, 2022 at 1:02 PM Yanteng Si <siyanteng@loongson.cn> wrote:
> >>
> >> update to commit 481cc97349d6 ("mm,doc: Add new
> >> documentation structure")
> >>
> >> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> >> ---
> >> .../translations/zh_CN/vm/bootmem.rst | 14 +++++++
> >> Documentation/translations/zh_CN/vm/index.rst | 37 +++++++++++++++----
> >> Documentation/translations/zh_CN/vm/oom.rst | 14 +++++++
> >> .../translations/zh_CN/vm/page_allocation.rst | 14 +++++++
> >> .../translations/zh_CN/vm/page_cache.rst | 14 +++++++
> >> .../translations/zh_CN/vm/page_reclaim.rst | 14 +++++++
> >> .../translations/zh_CN/vm/page_tables.rst | 14 +++++++
> >> .../translations/zh_CN/vm/physical_memory.rst | 14 +++++++
> >> .../translations/zh_CN/vm/process_addrs.rst | 14 +++++++
> >> Documentation/translations/zh_CN/vm/shmfs.rst | 14 +++++++
> >> Documentation/translations/zh_CN/vm/slab.rst | 14 +++++++
> >> Documentation/translations/zh_CN/vm/swap.rst | 14 +++++++
> >> .../translations/zh_CN/vm/vmalloc.rst | 14 +++++++
> >> 13 files changed, 198 insertions(+), 7 deletions(-)
> >> create mode 100644 Documentation/translations/zh_CN/vm/bootmem.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/oom.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/page_allocation.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/page_cache.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/page_reclaim.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/page_tables.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/physical_memory.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/process_addrs.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/shmfs.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/slab.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/swap.rst
> >> create mode 100644 Documentation/translations/zh_CN/vm/vmalloc.rst
> >
> > It's better to add above doc completely one by one, not just
> > unfinished few words.
> In the beginning, I thought so too.
>
> To be honest, My original intention was that a zh_CN update patch should
> equal an English patch. Because My commit simply updates vm/index.rst to
> 5.19rc-1. I don't know why there are so many empty files mixed in with
> the original patch(commit: 481cc97349d694e3211e14a886ad2b7ef55b5a2c).
>
> Of course, I'm willing to add them to the TODOLIST if you insist. :)
>
Uh, I understand these awkward empty files may imply a plan, but until now
It's just meaningless file, may not worth to translate them now. We'd
better leave
them off and do translation after some meaningful info added, and then the
translator sign will be more accountable. Is this good for you or any
more ideas?
Thanks
Alex
next prev parent reply other threads:[~2022-06-14 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 5:03 [PATCH v2 0/3] docs/zh_CN: Update the translation of vm to 5.19-rc1 Yanteng Si
2022-06-13 5:03 ` [PATCH v2 1/3] docs/zh_CN: Update the translation of highmem " Yanteng Si
2022-06-13 13:09 ` Wu X.C.
2022-06-13 5:03 ` [PATCH v2 2/3] docs/zh_CN: Update the translation of page_owner " Yanteng Si
[not found] ` <Yqc3HMCfwDlYabZI@bobwxc.mipc>
2022-06-15 8:13 ` YanTeng Si
2022-06-13 5:03 ` [PATCH v2 3/3] docs/zh_CN: Update the translation of vm index " Yanteng Si
2022-06-13 6:30 ` Alex Shi
2022-06-14 13:02 ` Yanteng Si
2022-06-14 13:42 ` Alex Shi [this message]
2022-06-15 2:38 ` YanTeng Si
2022-06-15 3:55 ` Alex Shi
2022-06-15 8:32 ` YanTeng Si
2022-06-13 13:09 ` Wu X.C.
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='CAJy-AmkAHT80n7BUfCi0kj4zMZYtUdG7q=WrUnnkUbg_mVZ4_g@mail.gmail.com' \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-doc@vger.kernel.org \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
--cc=zhoubinbin@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).