All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Harry Wei <harryxiyou@gmail.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: A problem about linux/Documentation/SubmittingPatches
Date: Wed, 2 Feb 2011 12:53:52 -0800	[thread overview]
Message-ID: <20110202205352.GA29053@kroah.com> (raw)
In-Reply-To: <20110202124633.e2380a77.rdunlap@xenotime.net>

On Wed, Feb 02, 2011 at 12:46:33PM -0800, Randy Dunlap wrote:
> On Thu, 3 Feb 2011 01:45:32 +0800 Harry Wei wrote:
> 
> > Hi us,
> >    I have seen linux-2.6.7/Documentation/SubmittingPatches but it hasn't described how to submit a translated document to kernel. I have also sent mail to <linux-kernel@zh-kernel.org>, however, there is no response.
> >    I have translated linux-2.6.37/Decumentation/SecurityBugs(no one translated it up to now). I'd like to send it to maintainers, then add it into kernel directories. However, I don't know how i can do it. Can anyone tell me howto do it? Thanks so much :)
> 
> Hi,
> 
> AFAIK, Greg KH handles all of the translation merging.
> 
> Right, Greg?

Yes, please feel free to send me any translations in patch form and I
will be glad to merge them.

thanks,

greg k-h

  reply	other threads:[~2011-02-02 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 17:45 A problem about linux/Documentation/SubmittingPatches Harry Wei
2011-02-02 20:46 ` Randy Dunlap
2011-02-02 20:53   ` Greg KH [this message]
     [not found]     ` <AANLkTikPM3m4D=qdzA0SHQG4J+ukH5jYSHC8zEMj_oH=@mail.gmail.com>
2011-02-03  2:44       ` Fwd: " Harry Wei
2011-02-03  2:48         ` Greg KH
     [not found]           ` <AANLkTikmDZW7oNRHXFs_6pGaM_-Y1e+zkhXnXjwuvbCB@mail.gmail.com>
2011-02-03  2:54             ` Fwd: " 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=20110202205352.GA29053@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=harryxiyou@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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.