> I interpreted your "So much for the linux-next tree" as saying "well, > that has been no help". I am sorry if I got that wrong.
True it didn't help in the merge that much this time. I don't think that is a problem with the linux-next tree but one of the lack of tty maintainer and tty tree letting the confusion occur in the first place - plus a large quantity of first time around ineptness on my part. > But my point above is that you had a fix for the current breakage in > Linus' tree a couple of weeks before you sent the patches to Linus that > broke the powerpc build (i.e. linux-next did its job) and yet you didn't > combine the fix with the original patch or send the fix with the original > patch. So we end up with a powerpc tree that won't build in the middle > of the merge window while more powerpc patches are trying to be > tested ... I understand that this could easily happen because of > forgetfulness, tiredness or accident. I really expected to get the rest merged within an hour or two, but then it broke, then I was travelling and each time I got wireless access to resync the tree and work on it - it broke again and again and again. Next time I will bump the patch up the pile and get it out earlier when that occurs. Alan _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev