>
> Oops. I wasn't going to tell anyone this yet, but since you've made
> this argument I feel I must be up front here....
>
> After CML2 has proven itself in 2.5, I do plan to go back to Marcelo
> and lobby for him accepting it into 2.4, on the grounds that doing so
> will simplify his maintainance task no end. That's why I'm tracking
> both sides of the fork in the rulebase, so it will be an easy drop-in
> replacement for Marcelo as well as Linus.
>
Don't do it!
A stable kernel should be stable also on the building tools.
When Marcelo will correct some grave potential security problem,
the user will rebuild the kernel and it will found that it must
install some other package (machine with 2.4 are now common,
python2 not yet so common) to secure his kernel, it would be
happy.
This is an example, but for a better maintainability you will
give serious problem to the novice kernel user.
giacomo
BTW there is alreay a punishment for you:
you will resync the variout ARCH, speak with various
subsystem maintainer, ... before to sent path to Marcelo.
-
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/