On Fri, Aug 26, 2011 at 09:32:52AM +0100, Russell King - ARM Linux wrote: > On Thu, Aug 25, 2011 at 10:23:21PM -0700, Olof Johansson wrote: > > Ok. Sounds like there might be some use for a temporary "work in > > progress" branch for linux-next for patches that are nearly ready to > > go but not quite that needs air time, but not really for anything > > beyond that. > > Bad idea. > > linux-next's policy is that everything in linux-next should be ready > for mainline - not nearly ready. > > Linus is threatening at the next merge window to ignore pull requests > from maintainers, and just pull the entire linux-next tree into his at > the beginning. Anything in linux-next which is "work in progress" will > therefore find its way immediately into mainline in whatever state it's > in. Are you referring to: > In fact, I'm seriously considering a rather draconian measure for next > merge window: I'll fetch the -next tree when I open the merge window, > and if I get anything but trivial fixes that don't show up in that "next > tree at the point of merge window open", I'll just ignore that pull > request. Because clearly people are just not being careful enough. I understood that he wants to check if the contents of a pull request are already in -next and otherwise just refuses to pull. SO nothing changes, except that you have to make sure your patches are in -next before the merge window opens. There may be something else on the lists I missed... Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
