> And you've completely ignored the real problem...which is when I get
> a text change for one tree, *how do I automatically propagate it to
> the other*? How do I *tell* that it ought to be propagated?
Depends on the context of the change.
In a majority of cases the answer is RTFC.
If this is too much effort, rethink your outlook on whats
involved as 'maintainer' of something like the Config.help's.
This is precisely the reason that splitting them was the best
thing that could have happened. They are now maintained by
the people who actually *know* whats involved, so you don't have to.
> Solutions that involve me doing an arbitrary and increasing amount of
> hand-hacking on every release are right out.
Reading diffs and finding out why things changed, and following
conversations on Linux-kernel are the only way you'll know if
something is relevant in other trees. If you've a robot that can
do this, I'm all ears, as it could save me hours each day.
-- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/