From: SeongJae Park <sj38.park@gmail.com>
To: gregkh@linuxfoundation.org
Cc: minchan@kernel.org, pyrasis@gamil.com, harryxiyou@gmail.com,
tshibata@ab.jp.nec.com, rob@landley.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 4/4] Documentation: ja_JP: Update broken link to tpp
Date: Fri, 6 Dec 2013 18:04:45 +0900 [thread overview]
Message-ID: <1386320685-28484-4-git-send-email-sj38.park@gmail.com> (raw)
In-Reply-To: <1386320685-28484-1-git-send-email-sj38.park@gmail.com>
Links for 'The Perfect Patch' which described on HOWTO document is
broken. Change those links to the copy at ozlabs.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
Documentation/ja_JP/HOWTO | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/ja_JP/HOWTO b/Documentation/ja_JP/HOWTO
index 8148a47..0091a82 100644
--- a/Documentation/ja_JP/HOWTO
+++ b/Documentation/ja_JP/HOWTO
@@ -149,7 +149,7 @@ linux-api@ver.kernel.org に送ることを勧めます。
この他にパッチを作る方法についてのよくできた記述は-
"The Perfect Patch"
- http://userweb.kernel.org/~akpm/stuff/tpp.txt
+ http://www.ozlabs.org/~akpm/stuff/tpp.txt
"Linux kernel patch submission format"
http://linux.yyz.us/patch-format.html
@@ -622,7 +622,7 @@ Linux カーネルコミュニティは、一度に大量のコードの塊を
これについて全てがどのようにあるべきかについての詳細は、以下のドキュメ
ントの ChangeLog セクションを見てください-
"The Perfect Patch"
- http://userweb.kernel.org/~akpm/stuff/tpp.txt
+ http://www.ozlabs.org/~akpm/stuff/tpp.txt
これらのどれもが、時にはとても困難です。これらの慣例を完璧に実施するに
は数年かかるかもしれません。これは継続的な改善のプロセスであり、そのた
--
1.8.1.2
prev parent reply other threads:[~2013-12-06 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 9:04 [PATCH 1/4] Documentation: HOWTO: Update broken links " SeongJae Park
2013-12-06 9:04 ` [PATCH 2/4] Documentation: ko_KR: Update broken link " SeongJae Park
2013-12-06 9:04 ` [PATCH 3/4] Documentation: zh_CN: " SeongJae Park
2013-12-06 9:04 ` SeongJae Park [this message]
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=1386320685-28484-4-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=pyrasis@gamil.com \
--cc=rob@landley.net \
--cc=tshibata@ab.jp.nec.com \
/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
all inboxes | Powered by JetHome®