linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@linux.alibaba.com>
To: alex.shi@linux.alibaba.com, harryxiyou@gmail.com, corbet@lwn.net,
	leoyang.li@nxp.com, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 01/42] docs/zh_CN: translate development-process into Chinese
Date: Wed, 27 Mar 2019 21:01:07 +0800	[thread overview]
Message-ID: <20190327130148.3258-2-alex.shi@linux.alibaba.com> (raw)
In-Reply-To: <20190327130148.3258-1-alex.shi@linux.alibaba.com>

Start development process translation.

Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Harry Wei <harryxiyou@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
 .../zh_CN/process/development-process.rst     | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 Documentation/translations/zh_CN/process/development-process.rst

diff --git a/Documentation/translations/zh_CN/process/development-process.rst b/Documentation/translations/zh_CN/process/development-process.rst
new file mode 100644
index 000000000000..500ca5056f60
--- /dev/null
+++ b/Documentation/translations/zh_CN/process/development-process.rst
@@ -0,0 +1,21 @@
+.. _cn_development_process_main:
+
+内核开发过程指南
+================
+
+内容:
+
+.. toctree::
+   :numbered:
+   :maxdepth: 2
+
+   1.Intro
+   2.Process
+   3.Early-stage
+   4.Coding
+   5.Posting
+   6.Followthrough
+   7.AdvancedTopics
+   8.Conclusion
+
+本文档的目的是帮助开发人员(及其经理)以最小的挫折感与开发社区合作。它试图记录这个社区如何以一种不熟悉Linux内核开发(或者实际上是自由软件开发)的人可以访问的方式工作。虽然这里有一些技术资料,但这是一个面向过程的讨论,不需要深入了解内核编程就可以理解。
-- 
2.19.1.856.g8858448bb


       reply	other threads:[~2019-03-27 13:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190327130148.3258-1-alex.shi@linux.alibaba.com>
2019-03-27 13:01 ` Alex Shi [this message]
2019-03-27 13:01 ` [PATCH 02/42] docs/zh_CN: add disclaimer and translator info in development-process Alex Shi
2019-03-27 13:01 ` [PATCH 03/42] docs/zh_CN: link development-process into process index Alex Shi
2019-03-27 13:01 ` [PATCH 04/42] docs/zh_CN: add Chinese 1.Intro file Alex Shi
2019-03-27 13:01 ` [PATCH 05/42] docs/zh_CN: add disclaimer and translator info into 1.Intro Alex Shi
2019-03-27 13:01 ` [PATCH 06/42] docs/zh_CN: add 2.Process.rst for development-process Alex Shi
2019-03-27 13:01 ` [PATCH 07/42] docs/zh_CN: add disclaimer and translator info in 2.Process Alex Shi
2019-03-27 13:01 ` [PATCH 08/42] docs/zh_CN: translate 3.Early-stage of development process Alex Shi
2019-03-27 13:01 ` [PATCH 09/42] docs/zh_CN: add disclaimer/translator info in 3.Early-stage Alex Shi
2019-03-27 13:01 ` [PATCH 10/42] docs/zh_CN: add 4.Coding.rst Alex Shi
2019-03-27 13:01 ` [PATCH 11/42] docs/zh_CN: add disclaimer and translator info in 4.Coding Alex Shi
2019-03-27 13:01 ` [PATCH 12/42] docs/zh_CN: add 5.Posting.rst into development-process Alex Shi
2019-03-27 13:01 ` [PATCH 13/42] docs/zh_CN: add disclaimer and translator info in 5.Posting Alex Shi
2019-03-27 13:01 ` [PATCH 14/42] docs/zh_CN: add the 6th doc 6.Followthrought.rst Alex Shi
2019-03-27 13:01 ` [PATCH 15/42] docs/zh_CN: add disclaimer and translator info in 6.Followthrough Alex Shi
2019-03-27 13:01 ` [PATCH 16/42] docs/zh_CN: translate 7.AdvanceTopics.rst Alex Shi
2019-03-27 13:01 ` [PATCH 17/42] docs/zh_CN: add disclaimer and translator info in 7.Advancedtopics Alex Shi
2019-03-27 13:01 ` [PATCH 18/42] docs/zh_CN: add 8.Conclusion.rst in development-process Alex Shi
2019-03-27 13:01 ` [PATCH 19/42] docs/zh_CN: add disclaimer and translator info in 8.Conclusion Alex Shi
2019-03-27 13:01 ` [PATCH 20/42] docs/zh_CN: add license-rules Chinese translation Alex Shi
2019-03-27 13:01 ` [PATCH 21/42] docs/zh_CN: fix links failure in license-rules Alex Shi
2019-03-27 13:01 ` [PATCH 22/42] docs/zh_CN: include Chinese translation header for license-rules Alex Shi
2019-03-27 13:01 ` [PATCH 23/42] docs/zh_CN: link the license-rules file into process index Alex Shi
2019-03-27 13:01 ` [PATCH 24/42] docs/zh_CN: add submit-checklist file Alex Shi
2019-03-27 13:01 ` [PATCH 25/42] docs/zh_CN: add disclaimer and transtlator info in submit-checklist Alex Shi
2019-03-27 13:01 ` [PATCH 26/42] docs/zh_CN: link the submit-checklist into process/index Alex Shi
2019-03-27 13:01 ` [PATCH 27/42] docs/zh_CN: add CoC doc Alex Shi
2019-03-27 13:01 ` [PATCH 28/42] docs/zh_CN: add disclaimer and translator info in CoC Alex Shi
2019-03-27 13:01 ` [PATCH 29/42] docs/zh_CN: link the CoC into process/index Alex Shi
2019-03-27 13:01 ` [PATCH 30/42] docs/zh_CN: add CoC interpretation Alex Shi
2019-03-27 13:01 ` [PATCH 31/42] docs/zh_CN: add disclaim and translator into CoC interp Alex Shi
2019-03-27 13:01 ` [PATCH 32/42] docs/zh_CN: link CoC interpretation into index Alex Shi
2019-03-27 13:01 ` [PATCH 33/42] docs/zh_CN: fix link issue in howto.rst Alex Shi
2019-03-27 13:01 ` [PATCH 34/42] docs/zh_CN: update howto.rst to latest version Alex Shi
2019-03-27 13:01 ` [PATCH 35/42] docs/zh_CN: update translator info and comments in howto Alex Shi
2019-03-27 13:01 ` [PATCH 36/42] docs/zh_CN: redirect license-rules to Chinese doc Alex Shi
2019-03-27 13:01 ` [PATCH 37/42] docs/zh_CN: redirect howto.rst link to Chinese version Alex Shi
2019-03-27 13:01 ` [PATCH 38/42] docs/zh_CN: update to latest submitting-patches.rst Alex Shi
2019-03-27 13:01 ` [PATCH 39/42] docs/zh_CN: update translator info in submitting-patches Alex Shi
2019-03-27 13:01 ` [PATCH 40/42] docs/zh_CN: redirect the submitting-patches to Chinese doc Alex Shi
2019-03-27 13:01 ` [PATCH 41/42] docs/zh_CN: redirect submit-checklist Alex Shi
2019-03-27 13:01 ` [PATCH 42/42] docs/zh_CN: update co-developed-by info after English version Alex Shi

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=20190327130148.3258-2-alex.shi@linux.alibaba.com \
    --to=alex.shi@linux.alibaba.com \
    --cc=corbet@lwn.net \
    --cc=harryxiyou@gmail.com \
    --cc=leoyang.li@nxp.com \
    --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 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).