From: Yunseong Kim <yskelg@gmail.com>
To: SeongJae Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Jinwoo Park <pmnxis@gmail.com>,
Austin Kim <austindh.kim@gmail.com>,
shjy180909@gmail.com, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] Documentation: cve Korean translation
Date: Thu, 20 Jun 2024 02:45:37 +0900 [thread overview]
Message-ID: <274c4648-e549-4b7e-a563-57d97e75dcc1@gmail.com> (raw)
In-Reply-To: <20240617231148.64366-1-sj@kernel.org>
Hi John, Hi SeongJae,
On 6/18/24 8:11 오전, SeongJae Park wrote:
> Hi John,
>
> On Mon, 17 Jun 2024 16:27:25 -0600 Jonathan Corbet <corbet@lwn.net> wrote:
>
>> yskelg@gmail.com writes:
>>
>>> From: Yunseong Kim <yskelg@gmail.com>
>>>
>>> This is a Documentation/process/cve korean version.
>>>
>>> The following changes have been updated based on SeongJae Park’s feedback
>>> from the last v4 patch.
>>>
>>> Signed-off-by: Yunseong Kim <yskelg@gmail.com>
>>> ---
>>> Documentation/translations/ko_KR/index.rst | 1 +
>>> .../translations/ko_KR/process/cve.rst | 107 ++++++++++++++++++
>>> 2 files changed, 108 insertions(+)
>>> create mode 100644 Documentation/translations/ko_KR/process/cve.rst
>>
>> SeongJae, are you happy with this version?
>
> I have a trivial concern about this patch. I'm not very confident about it,
> though. I therefore personally shared the concern with Yunseong. Yunseong
> thankfully agreed at some of my points, and he told me that he will post a new
> version of this patch.
Yeah, there are some parts that sound a bit awkward in Korean.
I think it needs a bit more work. I asked some friends to review it
offline. I think it would be better if I revise it a bit more before
sending it.
> Please correct me if anything is wrong or missed, Yunseong.
>
> So, I hope this patch to eventually be merged, but I have no strong opinion to
> provide either 'Reviewed-by:' or 'Nacked-by:'.
I'm trying to translate a little more naturally by looking at your
translation, All the documents you translated have been super helpful!
Thank you SungJae!
> [...]
>
>
> Thanks,
> SJ
Warm Regards,
Yunseong Kim
prev parent reply other threads:[~2024-06-19 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 1:08 [PATCH v5] Documentation: cve Korean translation yskelg
2024-06-17 22:27 ` Jonathan Corbet
2024-06-17 23:11 ` SeongJae Park
2024-06-19 17:45 ` Yunseong Kim [this message]
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=274c4648-e549-4b7e-a563-57d97e75dcc1@gmail.com \
--to=yskelg@gmail.com \
--cc=austindh.kim@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmnxis@gmail.com \
--cc=shjy180909@gmail.com \
--cc=sj@kernel.org \
--cc=workflows@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.