From: SeongJae Park <sj38.park@gmail.com>
To: corbet@lwn.net, paulmck@kernel.org
Cc: SeongJae Park <sjpark@amazon.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/5] Documentation/ko_KR/howto: Update a broken link
Date: Fri, 31 Jan 2020 21:52:36 +0100 [thread overview]
Message-ID: <20200131205237.29535-5-sj38.park@gmail.com> (raw)
In-Reply-To: <20200131205237.29535-1-sj38.park@gmail.com>
From: SeongJae Park <sjpark@amazon.de>
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 627ce97810d1..92840b7c63ef 100644
--- a/Documentation/translations/ko_KR/howto.rst
+++ b/Documentation/translations/ko_KR/howto.rst
@@ -328,7 +328,7 @@ Andrew Morton의 글이 있다.
거쳐야 한다. 이런 목적으로, 모든 서브시스템 트리의 변경사항을 거의 매일
받아가는 특수한 테스트 저장소가 존재한다:
- https://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git
+ https://git.kernel.org/?p=linux/kernel/git/next/linux-next.git
이런 식으로, linux-next 커널을 통해 다음 머지 기간에 메인라인 커널에 어떤
변경이 가해질 것인지 간략히 알 수 있다. 모험심 강한 테스터라면 linux-next
--
2.17.1
next prev parent reply other threads:[~2020-01-31 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 20:52 [PATCH 0/5] Documentation: Fix trivial nits SeongJae Park
2020-01-31 20:52 ` [PATCH 1/5] docs/locking: Fix outdated section names SeongJae Park
2020-01-31 20:52 ` [PATCH 2/5] docs/ko_KR/howto: Insert missing dots SeongJae Park
2020-02-05 17:15 ` Jonathan Corbet
2020-02-06 0:12 ` SeongJae Park
2020-01-31 20:52 ` [PATCH 3/5] Documentation/ko_KR/howto: Update broken web addresses SeongJae Park
2020-01-31 20:52 ` SeongJae Park [this message]
2020-01-31 20:52 ` [PATCH 5/5] Documentation/memory-barriers: Fix typos SeongJae Park
2020-01-31 21:23 ` Paul E. McKenney
2020-02-05 17:22 ` [PATCH 0/5] Documentation: Fix trivial nits 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=20200131205237.29535-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=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 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.