From: SeongJae Park <sj38.park@gmail.com>
To: corbet@lwn.net, minchan@kernel.org
Cc: mchehab@s-opensource.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 04/12] ko_KR/HOWTO: Update obsolete link to bugzilla faq
Date: Sat, 22 Oct 2016 00:19:49 +0900 [thread overview]
Message-ID: <20161021151957.8127-5-sj38.park@gmail.com> (raw)
In-Reply-To: <20161021151957.8127-1-sj38.park@gmail.com>
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
Documentation/ko_KR/HOWTO | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ko_KR/HOWTO b/Documentation/ko_KR/HOWTO
index 0b13d0a78446..4048297e48aa 100644
--- a/Documentation/ko_KR/HOWTO
+++ b/Documentation/ko_KR/HOWTO
@@ -325,7 +325,7 @@ http://patchwork.ozlabs.org/ 에 나열되어 있다.
bugzilla.kernel.org는 리눅스 커널 개발자들이 커널의 버그를 추적하는 곳이다.
사용자들은 발견한 모든 버그들을 보고하기 위하여 이 툴을 사용할 것을 권장한다.
kernel bugzilla를 사용하는 자세한 방법은 다음을 참조하라.
- http://test.kernel.org/bugzilla/faq.html
+ http://bugzilla.kernel.org/page.cgi?id=faq.html
메인 커널 소스 디렉토리에 있는 REPORTING-BUGS 파일은 커널 버그라고 생각되는
것을 보고하는 방법에 관한 좋은 템플릿이며 문제를 추적하기 위해서 커널
--
2.10.0
next prev parent reply other threads:[~2016-10-21 15:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 15:19 [PATCH 00/12] Fix and update HOWTO Korean translation SeongJae Park
2016-10-21 15:19 ` [PATCH 01/12] Documentation/HOWTO: Mark subsection in rst format SeongJae Park
2016-10-21 15:45 ` Mauro Carvalho Chehab
2016-10-21 16:42 ` SeongJae Park
2016-10-21 17:25 ` Mauro Carvalho Chehab
2016-10-21 17:57 ` SeongJae Park
2016-10-21 15:19 ` [PATCH 02/12] ko_KR/HOWTO: Fix a typo: s/Linux Torvalds/Linus Torvalds SeongJae Park
2016-10-21 15:19 ` [PATCH 03/12] ko_KR/HOWTO: Fix subtitles style SeongJae Park
2016-10-21 15:19 ` SeongJae Park [this message]
2016-10-21 15:19 ` [PATCH 05/12] ko_KR/HOWTO: Convert to ReST notation SeongJae Park
2016-10-21 15:19 ` [PATCH 06/12] ko_KR/HOWTO: Add cross-references to other documents SeongJae Park
2016-10-21 15:19 ` [PATCH 07/12] ko_KR/HOWTO: Update information about generating documentation SeongJae Park
2016-10-21 15:19 ` [PATCH 08/12] ko_KR/HOWTO: Improve some markups to make it visually better SeongJae Park
2016-10-21 15:19 ` [PATCH 09/12] ko_KR/HOWTO: Adjust external link references SeongJae Park
2016-10-21 15:19 ` [PATCH 10/12] ko_KR/HOWTO: Clean up bare :: lines SeongJae Park
2016-10-21 15:19 ` [PATCH 11/12] ko_KR/HOWTO: Add whitespace between URL and text SeongJae Park
2016-10-21 15:19 ` [PATCH 12/12] ko_KR/HOWTO: Mark subsection in rst format SeongJae Park
2016-10-21 20:47 ` [PATCH 00/12] Fix and update HOWTO Korean translation Jonathan Corbet
2016-10-22 1:39 ` SeongJae Park
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=20161021151957.8127-5-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=mchehab@s-opensource.com \
--cc=minchan@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.