From: "Justin P. Mattock" <justinmattock@gmail.com>
To: trivial@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Justin P. Mattock" <justinmattock@gmail.com>
Subject: [PATCH 35/35]Documentation/HOWTO update web address.
Date: Tue, 20 Jul 2010 21:52:52 -0700 [thread overview]
Message-ID: <1279687982-29413-5-git-send-email-justinmattock@gmail.com> (raw)
In-Reply-To: <1279687982-29413-1-git-send-email-justinmattock@gmail.com>
The patch below updates some borken web addresses.
Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
---
Documentation/HOWTO | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index 40ada93..365bda9 100644
--- a/Documentation/HOWTO
+++ b/Documentation/HOWTO
@@ -187,7 +187,7 @@ apply a patch.
If you do not know where you want to start, but you want to look for
some task to start doing to join into the kernel development community,
go to the Linux Kernel Janitor's project:
- http://janitor.kernelnewbies.org/
+ http://kernelnewbies.org/KernelJanitors
It is a great place to start. It describes a list of relatively simple
problems that need to be cleaned up and fixed within the Linux kernel
source tree. Working with the developers in charge of this project, you
@@ -315,7 +315,7 @@ process is tracked with the tool patchwork. Patchwork offers a web
interface which shows patch postings, any comments on a patch or
revisions to it, and maintainers can mark patches as under review,
accepted, or rejected. Most of these patchwork sites are listed at
-http://patchwork.kernel.org/ or http://patchwork.ozlabs.org/.
+http://patchwork.kernel.org/.
2.6.x -next kernel tree for integration tests
---------------------------------------------
@@ -595,7 +595,7 @@ start exactly where you are now.
----------
Thanks to Paolo Ciarrocchi who allowed the "Development Process"
-(http://linux.tar.bz/articles/2.6-development_process) section
+(http://lwn.net/Articles/94386/) section
to be based on text he had written, and to Randy Dunlap and Gerrit
Huizenga for some of the list of things you should and should not say.
Also thanks to Pat Mochel, Hanna Linder, Randy Dunlap, Kay Sievers,
--
1.7.1.rc1.21.gf3bd6
next prev parent reply other threads:[~2010-07-21 4:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 4:52 [PATCH 31/31]Documentation/filesystems/proc.txt " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 32/32]Documentation/filesystems/vfat.txt " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 33/33]Documentation/filesystems/affs.txt " Justin P. Mattock
2010-08-01 17:59 ` Geert Uytterhoeven
2010-08-01 18:07 ` Justin P. Mattock
2010-07-21 4:52 ` [PATCH 34/34]Documentation/filesystems/9p.txt " Justin P. Mattock
2010-07-21 4:52 ` Justin P. Mattock [this message]
2010-07-22 21:38 ` [PATCH 35/35]Documentation/HOWTO " Randy Dunlap
2010-07-22 22:31 ` Justin P. Mattock
2010-07-21 4:52 ` [PATCH 36/36]Documentation/hwmon/lm85 " Justin P. Mattock
2010-07-21 5:59 ` Mike Frysinger
2010-07-21 6:24 ` Justin P. Mattock
2010-07-21 4:52 ` [PATCH 37/37]Documentation/hwmon/via686a " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 38/38]Documentation/hwmon/smsc47m1 " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 39/39]Documentation/hwmon/w83627hf " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 40/40]Documentation/hwmon/gl518sm " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 41/41]Documentation/hwmon/thmc50 " Justin P. Mattock
2010-07-21 6:00 ` Thomas Weber
2010-07-21 6:44 ` Justin P. Mattock
2010-07-21 4:52 ` [PATCH 42/42]Documentation/hwmon/w83781d update wbe address Justin P. Mattock
2010-07-21 4:53 ` [PATCH 43/43]Documentation/hwmon/adm1026 update web address Justin P. Mattock
2010-07-21 6:00 ` Mike Frysinger
2010-07-21 6:04 ` Thomas Weber
2010-07-21 6:46 ` Justin P. Mattock
2010-07-21 4:53 ` [PATCH 44/44]Documentation/hwmon/w83792d update wbe address Justin P. Mattock
2010-07-21 4:53 ` [PATCH 45/45]Documentation/hwmon/k8temp update web address Justin P. Mattock
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=1279687982-29413-5-git-send-email-justinmattock@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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 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®