From: SeongJae Park <sj38.park@gmail.com>
To: corbet@lwn.net
Cc: SeongJae Park <sjpark@amazon.de>,
paulmck@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] docs/kokr: make reporting-bugs.rst obsolete
Date: Sun, 17 Jan 2021 11:09:30 +0100 [thread overview]
Message-ID: <20210117100931.9347-3-sj38.park@gmail.com> (raw)
In-Reply-To: <20210117100931.9347-1-sj38.park@gmail.com>
From: SeongJae Park <sjpark@amazon.de>
Translate this commit to Korean:
da514157c4f0 ("docs: make reporting-bugs.rst obsolete")
Signed-off-by: SeongJae Park <sjpark@amazon.de>
---
Documentation/translations/ko_KR/howto.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/ko_KR/howto.rst b/Documentation/translations/ko_KR/howto.rst
index 0a42ffdea918..787f1e85f8a0 100644
--- a/Documentation/translations/ko_KR/howto.rst
+++ b/Documentation/translations/ko_KR/howto.rst
@@ -345,7 +345,7 @@ https://bugzilla.kernel.org 는 리눅스 커널 개발자들이 커널의 버
https://bugzilla.kernel.org/page.cgi?id=faq.html
-메인 커널 소스 디렉토리에 있는 :ref:`admin-guide/reporting-bugs.rst <reportingbugs>`
+메인 커널 소스 디렉토리에 있는 'Documentation/admin-guide/reporting-issues.rst'
파일은 커널 버그라고 생각되는 것을 보고하는 방법에 관한 좋은 템플릿이며 문제를
추적하기 위해서 커널 개발자들이 필요로 하는 정보가 무엇들인지를 상세히 설명하고
있다.
--
2.17.1
next prev parent reply other threads:[~2021-01-17 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 10:09 [PATCH 0/3] docs: Update Korean translation SeongJae Park
2021-01-17 10:09 ` [PATCH 1/3] Documentation/kokr/howto: Replace HTTP links with HTTPS ones: Documentation/process SeongJae Park
2021-01-17 10:09 ` SeongJae Park [this message]
2021-01-17 10:09 ` [PATCH 3/3] docs/kokr: Link memory-barriers.txt to rst SeongJae Park
2021-01-18 20:04 ` [PATCH 0/3] docs: Update Korean translation Jonathan Corbet
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=20210117100931.9347-3-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sjpark@amazon.de \
/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).