Yanteng Si <siyanteng@xxxxxxxxxxx> writes: > 在 2023/8/14 10:40, Gang Li 写道: >> Hi, >> >> On 2023/8/12 19:00, Yanteng Si wrote: >>> 在 2023/8/11 16:08, Gang Li 写道: >>>> +译注： >>>> +本文仅为方便汉语阅读，不保证与英文版本同步; >>>> +若有疑问，请阅读英文版本; >>>> +若有翻译问题，请通知译者； >>>> +若想修改文档，也请先修改英文版本。 >>> >>> In fact, we already have an easier way to do this, just include >>> disclaimer-zh_CN. >>> >>> If you observe the files under .../zh_CN/, they all have a similar >>> header, and we can completely follow them. >>> >> Thanks. I just noticed that there are txt files under >> "zh_CN/arch/arm64/" and "zh_CN/video4linux/". They have the same >> header, and I will >> refer to them in v2. >> >>> But you should also have noticed that memory-barriers are not a >>> standard rst file and will not be built, which will result in it only >>> staying in the development tree. >>> It won't appear at: >> https://docs.kernel.org >> https://www.kernel.org/doc/html/latest/ >> >> But people can still access the txt document in this way: >> https://www.kernel.org/doc/Documentation/memory-barriers.txt >> >>> Finally, this patch is too huge and we may need some time to review it. >>> >> Of course. Would it be more convenient if I split the file into multiple >> patches and send them as one series? > You didn't have to. > > > If you want to send a series, you can refactor the original document > into rst format and make it the first patch of the series. > > Just like: > > [PATCH v2 0/2] docs: Refactor memory-barriers.txt and translate it into > Chinese > > [PATCH v2 1/2] docs: convert memory-barriers.txt to RST For $REASONS, memory-barriers.txt is staying as .txt, thus, as Gang Li pointed out, the wrapper page that pulls it in. The proper solution is to create a wrapper for the translated .txt file as well. Thanks, jon
