Julian Gilbey <[EMAIL PROTECTED]> writes: > Here's another suggestion. Why not leave the existing emacsen > packages as they are and apply the rule only to new versions of emacs > (so emacs21 and xemacs22 onwards)? That will save the hassle, I > guess.
That sounds like a pretty good solution, actually, and according to dres, xemacs doesn't have this problem anyway. I'll fix it for emacs in emacs21, but I'll go ahead and change policy sooner. I wonder what that means I should do with this bug. Should it be set to fixed once emacsen-common's policy is fixed and a bug filed against emacs20, or what. -- Rob Browning rlb @defaultvalue.org, @linuxdevel.com, and @debian.org Previously @cs.utexas.edu GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
