A question about -mm tree and -next tree.
I know that -next tree is doing these things daily: 1. reset HEAD to HEAD of linus's tree 2. merge about 221 subsytem trees automatically And I know that -mm tree : 1. contains patches which are going to applied into latest Linus release (3.x or 3.x-rcY) 2. most of the patches are included in -next (this is the original purpose of the -next tree - to reduce Andres Mortan's stress and make the patches more tested) So here comes my questions: I found that most of the -mm patches are in -next, which means they will be tested more by all developers , but there are still some patches are not included in -next tree. So why are they special and how they make their way into Linus 's mainline code ? -- Regards, Zhan Jianyu
On Tue, 06 Aug 2013 21:27:27 +0800, Zhan Jianyu said:
I found that most of the -mm patches are in -next, which means they will be tested more by all developers , but there are still some patches are not included in -next tree. So why are they special and how they make their way into Linus 's mainline code ?
In general, the ones that are in Andrew's -mm tree but not in the main linux-next tree are ones that aren't ready for prime time - either they have design issues, or need extensive runtime testing before people are convinced they're right. Think of it this way: Greg HK runs the staging/ area for drivers that still need work, and Andrew runs -mm for single patches that still need work.
participants (2)
-
Valdis.Kletnieks＠vt.edu -
Zhan Jianyu