On Wednesday, 30 of April 2008, David Miller wrote:

quoted text
>

> This is starting to get beyond frustrating for me.

>

> Yesterday, I spent the whole day bisecting boot failures

> on my system due to the totally untested linux/bitops.h

> optimization, which I fully analyzed and debugged.

>

> Today, I had hoped that I could get some work done of my

> own, but that's not the case.

>

> Yet another bootup regression got added within the last 24

> hours.

>

> I don't mind fixing the regression or two during the merge

> window but THIS IS ABSOLUTELY, FUCKING, REDICULIOUS!

>

> The tree breaks every day, and it's becomming an extremely

> non-fun environment to work in.

>

> We need to slow down the merging, we need to review things

> more, we need people to test their fucking changes!

Well, I must say I second that.
I'm not seeing regressions myself this time (well, except for the one that

Jiri fixed), but I did find a few of them during the post-2.6.24 merge window

and I wouldn't like to repeat that experience, so to speak.
IMO, the merge window is way too short for actually testing anything.  I rebuild

the kernel once or even twice a day and there's no way I can really test it.

I can only check if it breaks right away.  And if it does, there's no time to

find out what broke it before the next few hundreds of commits land on top of

that.
Thanks,

Rafael

--

unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

the body of a message to majordomo@vger.kernel.org

More majordomo info at  http://vger.kernel.org/majordomo-info.html

Please read the FAQ at  http://www.tux.org/lkml/