From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org, linux-kernel@zh-kernel.org,
synmyth@gmail.com, zhangyangjing@gmail.com,
wangxiaochen0@gmail.com, yaxinsn@163.com
Subject: [PATCH v3 0/2]Documentation/zh_CN: Fix messy code files
Date: Sun, 12 Jun 2011 11:33:48 +0800 [thread overview]
Message-ID: <20110612033343.GA4321@gmail.com> (raw)
From: Harry Wei <harryxiyou@gmail.com>
This is v3 patches for fixing the messy code files,
Documentation/zh_CN/email-clients.txt and
Documentation/zh_CN/SubmitChecklist.
v3's new figures.
Combine the remove and add back operations to one single patch.
So now we have only two patches for fixing this problem.
Harry Wei (2)
Documentation/zh_CN: Fix messy code file email-clients.txt
Documentation/zh_CN: Fix messy code file SubmitChecklist
Thanks
Harry Wei
next reply other threads:[~2011-06-12 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 3:33 Harry Wei [this message]
2011-06-25 8:43 ` [PATCH v3 0/2]Documentation/zh_CN: Fix messy code files Harry Wei
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=20110612033343.GA4321@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kernel@zh-kernel.org \
--cc=synmyth@gmail.com \
--cc=wangxiaochen0@gmail.com \
--cc=yaxinsn@163.com \
--cc=zhangyangjing@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