On Sat, 2002-08-31 at 18:38, Stephen J. Turnbull wrote:
I don't want to _move_ stuff out of 21.4 until it's been
beaten on a
bit by the testers.
Ok, I guess 21.5 is the place to test this kind of stuff. Here's a
suggestion how to proceed with this:
1) Copy applicable stuff from 21.5's files.el to corresponding files
2) Roll these packages into pre-release, test with 21..
3) No breakage -> remove the duplicated entries from 21.5's files.el.
4) No breakage -> remove the duplicated entries from 21.4's files.el.
5) No breakage -> move the affected packages to stable dirs.
Any reported breakage would roll back the whole chain of changes.
There are also some cases where there are shadows in the alist. I
think it's probably a good idea to keep any shadowing regexps in the
defvar in the appropriate order, at least for now.
Ok. I'll have a look at those shadows if they're still valid and can't
be worked around.
Note that add-to-list doesn't protect us at all if somebody
regexp, eg from "\\.tex$" to "\\.\\(tex\\|sty\\)$".
True, but add-to-list (without the new &optional APPEND) inserts stuff
at the beginning of the list, so it should be safe, assuming that the
list is processed from begin to end. The add-to-list'ed entries could
cause some shadows, but wouldn't break anything, no?
ville.skytta at xemacs.org