aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Nordholts <enselic@gmail.com>2013-07-24 23:17:34 -0700
committerJiri Kosina <jkosina@suse.cz>2013-07-25 12:37:24 +0200
commit297957b4a82f70d3bc6fbac7f6051ed0e5806f9b (patch)
treea19d2f004e1ae0a35f9438bd242fe949d931a7be
parent36019265cf81cdb2d366b28016bb00b936efc751 (diff)
Documentation: development-process: Update -mm and -next URLs
Both old URLs are broken, so update them. Signed-off-by: Martin Nordholts <enselic@gmail.com> Acked-by: Rob Landley <rob@landley.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
-rw-r--r--Documentation/development-process/2.Process4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/development-process/2.Process b/Documentation/development-process/2.Process
index 4823577c650..2e0617936e8 100644
--- a/Documentation/development-process/2.Process
+++ b/Documentation/development-process/2.Process
@@ -276,7 +276,7 @@ mainline get there via -mm.
The current -mm patch is available in the "mmotm" (-mm of the moment)
directory at:
- http://userweb.kernel.org/~akpm/mmotm/
+ http://www.ozlabs.org/~akpm/mmotm/
Use of the MMOTM tree is likely to be a frustrating experience, though;
there is a definite chance that it will not even compile.
@@ -287,7 +287,7 @@ the mainline is expected to look like after the next merge window closes.
Linux-next trees are announced on the linux-kernel and linux-next mailing
lists when they are assembled; they can be downloaded from:
- http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/
+ http://www.kernel.org/pub/linux/kernel/next/
Some information about linux-next has been gathered at: