workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yunseong Kim <yskelg@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: skhan@linuxfoundation.org, 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,
	linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v3] Documentation: cve Korean translation
Date: Mon, 27 May 2024 22:21:44 +0900	[thread overview]
Message-ID: <bf37bf39-32d3-457f-abd6-115215d631af@gmail.com> (raw)
In-Reply-To: <87ikyzpgqz.fsf@meer.lwn.net>



On 5/27/24 9:43 오후, Jonathan Corbet wrote:
> yskelg@gmail.com writes:
> 
>> From: Yunseong Kim <yskelg@gmail.com>
>>
>> This is a Documentation/process/cve korean version.
> 
> Thank you for working to improve our documentation.  A couple of
> questions, though:

Hi Jonathan, Thank you for the review.

>> Reviewed-by: Jinwoo Park <pmnxis@gmail.com>
>> Signed-off-by: Yunseong Kim <yskelg@gmail.com>
> 
> 1) Why do I have three versions of it in my mailbox, sent over a period
>    of 13 minutes?  What changed between the versions?

Sorry, I forgot the name of the reviewer when I first sent the
documentation content related patch version 2.

>    Normally, you want to wait for reviews to come in on one version
>    before posting the next, and you should put a comment after the "---"
>    line saying what changed.
> 
> 2) When did this review from Jinwoo Park happen?  I was not copied on
>    that.
> Thanks,
> 
> jon

Thank you for your comment.

I have updated the content from version 2 to version 1 from
Jinwoo's review.

In version 3, I added the name of the reviewer I forgot in version 2.

> ---
>  .../translations/ko_KR/process/cve.rst        | 108 ++++++++++++++++++
>  1 file changed, 108 insertions(+)
>  create mode 100644 Documentation/translations/ko_KR/process/cve.rst
>
> diff --git a/Documentation/translations/ko_KR/process/cve.rst
b/Documentation/translations/ko_KR/process/cve.rst
> new file mode 100644
> index 000000000000..9daacba8d445
> --- /dev/null
> +++ b/Documentation/translations/ko_KR/process/cve.rst
> @@ -0,0 +1,108 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +:원문: Documentation/process/cve.rst
> +:역자: 김윤성 <yskelg@gmail.com>

I added Jinwoo's name here on version 3.

> +:감수: 박진우 <pmnxis@gmail.com>

Warm Regards,

Yunseong Kim

  reply	other threads:[~2024-05-27 13:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 10:30 [PATCH v3] Documentation: cve Korean translation yskelg
2024-05-27 12:43 ` Jonathan Corbet
2024-05-27 13:21   ` Yunseong Kim [this message]
2024-05-27 13:50     ` Jonathan Corbet
2024-05-27 14:43       ` Yunseong Kim
2024-05-27 14:55         ` Jonathan Corbet
2024-05-27 17:00           ` Jinwoo Park
2024-05-30  1:43 ` SeongJae Park
2024-05-30 11:46   ` Yunseong Kim

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=bf37bf39-32d3-457f-abd6-115215d631af@gmail.com \
    --to=yskelg@gmail.com \
    --cc=austindh.kim@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmnxis@gmail.com \
    --cc=shjy180909@gmail.com \
    --cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).