linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Teo <eugeneteo@kernel.sg>
To: Li Yang <leoli@freescale.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
	xiyou.wangcong@gmail.com, bryan.wu@analog.com,
	TripleX Chung <xxx.phy@gmail.com>,
	Maggie Chen <chenqi@beyondsoft.com>
Subject: Re: [PATCH] Chinese translation of Documentation/HOWTO
Date: Thu, 21 Jun 2007 23:29:58 +0800	[thread overview]
Message-ID: <20070621152958.GA23761@kernel.sg> (raw)
In-Reply-To: <1182436817579-git-send-email-leoli@freescale.com>

<quote sender="Li Yang">
> This is a Chinese translated version of Documentation/HOWTO.  Currently
> Chinese involvement in Linux kernel is very low, especially comparing to
> its largest population base.  Language could be the main obstacle.  Hope
> this document will help more Chinese to contribute to Linux kernel.
> 
> Signed-off-by: Li Yang <leoli@freescale.com>
> Signed-off-by: TripleX Chung <xxx.phy@gmail.com>
> Signed-off-by: Maggie Chen <chenqi@beyondsoft.com>
> ---
> Address comments from Wang Cong.
>  Documentation/zh_CN/HOWTO |  536 +++++++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 536 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/zh_CN/HOWTO
> 
> diff --git a/Documentation/zh_CN/HOWTO b/Documentation/zh_CN/HOWTO
> new file mode 100644
> index 0000000..c70debd
> --- /dev/null
> +++ b/Documentation/zh_CN/HOWTO
[...]

I read through the translated HOWTO. Looks good to me.

Eugene


  parent reply	other threads:[~2007-06-21 15:30 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 14:40 [PATCH] Chinese translation of Documentation/HOWTO Li Yang
2007-06-21 15:18 ` WANG Cong
2007-06-21 15:29 ` Eugene Teo [this message]
2007-06-21 16:23 ` Bryan Wu
2007-06-22  2:48 ` Rob Landley
2007-06-22  3:23   ` dave young
2007-06-22  5:33     ` Rob Landley
2007-06-22  6:07       ` dave young
2007-06-22 18:45         ` Rob Landley
2007-06-22  6:09       ` Li Yang-r58472
2007-06-22  9:21       ` Alan Cox
2007-06-22 18:53         ` Rob Landley
2007-06-22  3:58   ` Li Yang-r58472
2007-06-22  4:22     ` Bryan Wu
2007-06-22  5:12     ` WANG Cong
2007-06-22 17:02     ` Linus Torvalds
2007-06-22 17:16       ` Tomas Neme
2007-06-22 18:39       ` TripleX
2007-06-22 18:58         ` Li, Tong N
2007-06-22 21:00         ` Rob Landley
2007-06-22 19:11       ` Rob Landley
2007-06-23  4:53         ` WANG Cong
2007-06-28 17:53       ` Pavel Machek
2007-06-29 18:22         ` Rob Landley
2007-06-22  5:29   ` Rob Landley
     [not found] <a8e1da0706191858w73a453dfjf28895150af85cfe@mail.gmail.com>
2007-06-20  5:13 ` Li Yang-r58472
2007-06-20  5:22   ` dave young
2007-06-20  5:57     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2007-06-19 14:21 Li Yang
2007-06-19 15:26 ` Li Yang-r58472
2007-06-19 15:31   ` Greg KH
2007-06-17 19:19     ` Pavel Machek
2007-06-24 16:34       ` Alan Cox
2007-06-24 16:43         ` Rene Herman
2007-06-19 15:36 ` WANG Cong
2007-06-19 16:14   ` Li Yang-r58472
2007-06-20  5:09     ` WANG Cong
2007-06-20  2:52 ` Bryan Wu

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=20070621152958.GA23761@kernel.sg \
    --to=eugeneteo@kernel.sg \
    --cc=bryan.wu@analog.com \
    --cc=chenqi@beyondsoft.com \
    --cc=gregkh@suse.de \
    --cc=leoli@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    --cc=xxx.phy@gmail.com \
    /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).