From 9346419d188a2c39eecc7d084937626363e4f653 Mon Sep 17 00:00:00 2001 From: Randy Dunlap Date: Sun, 23 May 2010 17:02:30 -0700 Subject: [PATCH] --- yaml --- r: 198005 b: refs/heads/master c: e6a591e58e2c70912987f9f19d36ba967063b251 h: refs/heads/master i: 198003: 737a2b7fe7d6a403c2e635b23ca154b23025927d v: v3 --- [refs] | 2 +- trunk/Documentation/development-process/2.Process | 14 ++++++++------ 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/[refs] b/[refs] index db6d31a9766b..21024e9e3bb8 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: ef0eba477eeb424db97a162eb3a8c887b9c619df +refs/heads/master: e6a591e58e2c70912987f9f19d36ba967063b251 diff --git a/trunk/Documentation/development-process/2.Process b/trunk/Documentation/development-process/2.Process index 11682b120e8d..97726eba6102 100644 --- a/trunk/Documentation/development-process/2.Process +++ b/trunk/Documentation/development-process/2.Process @@ -267,12 +267,8 @@ an appropriate subsystem tree or be sent directly to Linus. In a typical development cycle, approximately 10% of the patches going into the mainline get there via -mm. -The current -mm patch can always be found from the front page of - - http://kernel.org/ - -Those who want to see the current state of -mm can get the "-mm of the -moment" tree, found at: +The current -mm patch is available in the "mmotm" (-mm of the moment) +directory at: http://userweb.kernel.org/~akpm/mmotm/ @@ -307,6 +303,12 @@ volatility of linux-next tends to make it a difficult development target. See http://lwn.net/Articles/289013/ for more information on this topic, and stay tuned; much is still in flux where linux-next is involved. +Besides the mmotm and linux-next trees, the kernel source tree now contains +the drivers/staging/ directory and many sub-directories for drivers or +filesystems that are on their way to being added to the kernel tree +proper, but they remain in drivers/staging/ while they still need more +work. + 2.5: TOOLS