From: Minchan Kim <minchan@kernel.org>
To: "Lee, Jae-Hong" <pyrasis@gmail.com>
Cc: rob@landley.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] correct unfaithful translation on HOWTO in ko_KR
Date: Wed, 31 Jul 2013 23:43:48 +0900 [thread overview]
Message-ID: <20130731144348.GB7641@gmail.com> (raw)
In-Reply-To: <1375278775-3430-2-git-send-email-pyrasis@gmail.com>
On Wed, Jul 31, 2013 at 10:52:54PM +0900, Lee, Jae-Hong wrote:
> From: "Lee, Jae-Hong" <pyrasis@gmail.com>
>
> Signed-off-by: Lee, Jae-Hong <pyrasis@gmail.com>
Acked-by: Minchan Kim <minchan@kernel.org>
Thanks!
--
Kind regards,
Minchan Kim
next parent reply other threads:[~2013-07-31 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1375278775-3430-1-git-send-email-pyrasis@gmail.com>
[not found] ` <1375278775-3430-2-git-send-email-pyrasis@gmail.com>
2013-07-31 14:43 ` Minchan Kim [this message]
2013-07-31 14:45 ` [PATCH 2/3] correct unfaithful translation on HOWTO in ko_KR Minchan Kim
[not found] ` <1375278775-3430-3-git-send-email-pyrasis@gmail.com>
2013-07-31 14:47 ` [PATCH 3/3] type fix on stable_api_nonsense.txt " Minchan Kim
[not found] ` <20130731143936.GA7641@gmail.com>
2013-08-01 13:03 ` [PATCH 1/3] type fix on HOWTO " Lee, Jae-Hong
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=20130731144348.GB7641@gmail.com \
--to=minchan@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pyrasis@gmail.com \
--cc=rob@landley.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox