From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4]Documentation/zh_CN: Remove messy code documentations and rebuild new documentations
Date: Sat, 11 Jun 2011 22:32:15 -0700 [thread overview]
Message-ID: <20110612053215.GA18418@kroah.com> (raw)
In-Reply-To: <20110612025319.GA2035@gmail.com>
On Sun, Jun 12, 2011 at 10:53:21AM +0800, Harry Wei wrote:
> On Sat, Jun 11, 2011 at 01:05:13PM -0700, Greg KH wrote:
> > On Sat, Jun 11, 2011 at 10:37:52AM +0800, Harry Wei wrote:
> > > From: Harry Wei <harryxiyou@gmail.com>
> > >
> > > There are two messy code documentations in our
> > > Documentation/zh_CN/ directory. They are
> > > Documentation/zh_CN/email-clients.txt &
> > > Documentation/zh_CN/SubmitChecklist.
> > > The following patches can fix them.
> > >
> > > Harry Wei (4)
> > > Documentation/zh_CN: remove messy code file email-clients.txt
> > > Documentation/zh_CN: remove messy code file SubmitChecklist
> > > Documentation/zh_CN: add new file email-clients.txt
> > > Documentation/zh_CN: add new file SubmitChecklist
> >
> > Why are you deleting and then adding back the files?
> > Why not just edit them and change them in one single patch?
> Hmmm..., what about two patches? One for editing and changing
> email-clients.txt and the other one for editing and changing
> SubmitChecklist.
That is fine, I'll queue them up in a few days.
greg k-h
next prev parent reply other threads:[~2011-06-12 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 2:37 [PATCH v2 0/4]Documentation/zh_CN: Remove messy code documentations and rebuild new documentations Harry Wei
2011-06-11 20:05 ` Greg KH
2011-06-12 2:53 ` Harry Wei
2011-06-12 5:32 ` Greg KH [this message]
2011-06-12 8:27 ` 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=20110612053215.GA18418@kroah.com \
--to=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.