> > Can we agree that it makes sense to add features one-by-one when
> > they are independent?
> Oh absolutely, and have you looked at the current factoring?
> This is still being improved, of course.
Actually, I was about to answer that issue in a reply to the mail by
Thunder, where he said that he can do a lot of patches, which do not have
any effect. Sam did actually state it already, it's not about adding which
have no effect, it's about patches which do change one thing at a time. N
patches which don't change anything and then number N+1 which changes
everything doesn't help the situation at all.
> Well, actually a lot of the work done by Kai is simply importing
> portions of Keith's work that break out easily, which is purely
> duplication of effort, since such work is already in progress. In
> fact it creates more work, because then we have to go parse Kai's
> patches and find out what he submitted, then see if it gets applied
> so we can mark it 'applied' in the list. This is a real waste of
> time, and did I mention, it's divisive?
Well, thanks. Maybe you have an example of what you mean above? If I take
other people's work, I credit them, and I don't think I did so far at all,
but definitely not "a lot".
I will surely pick pieces, though - this is what this process is all
Anyway, since you don't understand anything about the internals of the
kbuild process at all (neither kbuild-2.4 nor 2.5), as you now proved
publically multiple times, but are just aiming at proving your abilities
in making politics on l-k, don't expect me to answer any further mails on
this (and save yourself the effort to reply to this one, but I know you
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/