All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 04/12] ko_KR/HOWTO: Update obsolete link to bugzilla faq
Date: Tue,  1 Nov 2016 05:27:13 +0900	[thread overview]
Message-ID: <20161031202721.8068-5-sj38.park@gmail.com> (raw)
In-Reply-To: <20161031202721.8068-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 1a5d7a8d66be..f3348ef68bbd 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
 
 메인 커널 소스 디렉토리에 있는 admin-guide/reporting-bugs.rst 파일은 커널 버그라고 생각되는
 것을 보고하는 방법에 관한 좋은 템플릿이며 문제를 추적하기 위해서 커널
-- 
2.10.0

  parent reply	other threads:[~2016-10-31 20:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 20:27 [PATCH v2 00/12] Fix and update HOWTO Korean translation SeongJae Park
2016-10-31 20:27 ` [PATCH v2 01/12] Documentation/process/howto: Mark subsection in suggested format SeongJae Park
2016-10-31 20:27 ` [PATCH v2 02/12] ko_KR/HOWTO: Fix a typo: s/Linux Torvalds/Linus Torvalds SeongJae Park
2016-10-31 20:27 ` [PATCH v2 03/12] ko_KR/HOWTO: Fix subtitles style SeongJae Park
2016-10-31 20:27 ` SeongJae Park [this message]
2016-10-31 20:27 ` [PATCH v2 05/12] ko_KR/HOWTO: Convert to ReST notation SeongJae Park
2016-10-31 20:27 ` [PATCH v2 06/12] ko_KR/HOWTO: Add cross-references to other documents SeongJae Park
2016-10-31 20:27 ` [PATCH v2 07/12] ko_KR/HOWTO: Update information about generating documentation SeongJae Park
2016-10-31 20:27 ` [PATCH v2 08/12] ko_KR/HOWTO: Improve some markups to make it visually better SeongJae Park
2016-10-31 20:27 ` [PATCH v2 09/12] ko_KR/HOWTO: Adjust external link references SeongJae Park
2016-10-31 20:27 ` [PATCH v2 10/12] ko_KR/HOWTO: Clean up bare :: lines SeongJae Park
2016-10-31 20:27 ` [PATCH v2 11/12] ko_KR/HOWTO: Add whitespace between URL and text SeongJae Park
2016-10-31 20:27 ` [PATCH v2 12/12] ko_KR/HOWTO: Mark subsection in suggested format SeongJae Park
2016-11-06 18:21 ` [PATCH v2 00/12] Fix and update HOWTO Korean translation SeongJae Park
2016-11-06 20:45   ` Jonathan Corbet
2016-11-08  0:05 ` Jonathan Corbet
2016-11-08  1:30   ` 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=20161031202721.8068-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.