Re: MI: frozen variable objects

[Nick Roberts <nickrob at snap dot net dot nz>]

 > > If the changes go in after the release I generally have six months to spot
 > > a bug, if they go in now I'll have roughly two weeks.
 > 
 > I don't get the fuss.  It's not an immensely destabilizing change or a
 > huge new subsystem.  Why should it be treated separately from any other
 > patch posted in the last few months, in the later half of a release
 > gap?

Since you are confident it DTRT, I guess there is no problem.  More importantly
you have the authority, so just do it.  Richard Stallman has no such qualms
(he calls it "exercising leadership").

Now Vladimir fetches values in one place, I have a small patch on top of that
which updates references properly, I think.

 >...
 > I appreciate that you fix things, especially those MI PRs.  I will
 > somehow get to them.  But, good lord, I need more help from other
 > maintainers!
 > 
 > And more maintainers.  All: Should Nick be an MI maintainer now?

I would just commit small patches (like -var-set-format) and try to provide
support for the larger ones (like Variable objects laziness).

-- 
Nick                                           http://www.inet.net.nz/~nickrob