Dave Jones <davej@suse.de>:
> As you obviously completely ignored my previous point, I'll reiterate it.
>
> 1. You run Linus' split-into-config.in script on a 2.4 tree.
> 2. You add whatever Config.ins have been updated to the 2.4 config.ins
> 3. You regenerate with the find example I showed in the other mail.
>
> There. 2.4 Configure.help up to date with latest symbols, but
> containing none of the 2.5 ones.
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?
It's not sufficient to develop a one-shot conversion procedure. What
I came up with had to allow me to continue generating correct help
files for all trees under the assumption that text changes for 2.4
could come in against the 2.5 copy of the help entry, or vice-versa --
bearing in mind that some symbols have divergent text and that's correct.
Solutions that involve me doing an arbitrary and increasing amount of
hand-hacking on every release are right out.
If you think this problem through, I'm sure you'll come up with a
design very similar to what I actually built. Which, by Linus's
choice, got irrecoverably nuked.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a> - 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/
This archive was generated by hypermail 2b29 : Fri Feb 15 2002 - 21:01:10 EST