On 2019/3/5 6:06 上午, Li Yang wrote:
> On Sun, Mar 3, 2019 at 10:03 PM Alex Shi <alex....@linux.alibaba.com> wrote:
>> This a disclaimer file which will be included in Chinese files
>> as header. To reduce the same common contents copy.
> It is great for reducing the duplication.  But since this is in the
> translation folder, probably it will be even better to include a
> translated version of this disclaimer too?

Sure, I will update it with Chinese words. and resend whole threads.

Thanks Leo!

> Regards,
> Leo
>
>> Most of contents quoted from Federico Vaga's file:
>> Documentation/translations/it_IT/disclaimer-ita.rst.
>> Thanks a lot!
>>
>> Signed-off-by: Alex Shi <alex....@linux.alibaba.com>
>> Cc: Harry Wei <harryxi...@gmail.com>
>> Cc: Jonathan Corbet <cor...@lwn.net>
>> Cc: Li Zefan <lize...@huawei.com>
>> Cc: Shawn Guo <shawn....@linaro.org>
>> Cc: Fengguang Wu <fengguang...@intel.com>
>> Cc: Coly Li <col...@suse.de>
>> Cc: Federico Vaga <federico.v...@vaga.pv.it>
>> ---
>>  Documentation/translations/zh_CN/disclaimer-zh_CN.rst | 11 +++++++++++
>>  1 file changed, 11 insertions(+)
>>  create mode 100644 Documentation/translations/zh_CN/disclaimer-zh_CN.rst
>>
>> diff --git a/Documentation/translations/zh_CN/disclaimer-zh_CN.rst 
>> b/Documentation/translations/zh_CN/disclaimer-zh_CN.rst
>> new file mode 100644
>> index 000000000000..0de5dfb069ca
>> --- /dev/null
>> +++ b/Documentation/translations/zh_CN/disclaimer-zh_CN.rst
>> @@ -0,0 +1,11 @@
>> +:orphan:
>> +
>> +.. warning::
>> +   The purpose of this file is to be easier to read and understand for 
>> Chinese
>> +   speakers and is not intended as a fork. So, if you have any comments or
>> +   updates for this file please try to update the original English file 
>> first.
>> +
>> +.. note::
>> +   If you find any difference between this document and the original file 
>> or a
>> +   problem with the translation, please contact the maintainer of this file,
>> +   or get help from Alex Shi <alex....@linux.alibaba.com>
>> --
>> 2.19.1.856.g8858448bb
>>
>

Reply via email to