[slime-devel] Re: Making potentially problematic changes

[Marco Baringer]

Ian Eslick wrote:
> I've updated the inspector in swank.lisp to support metaclass based slot-value overrides.  This requires use of the mop functions slot-boundp-using-class and slot-value-using-class (and adding them to the swank-mop package) which may not be consistent over the various versions.  Since the inspector is rather central to slime, I don't want to commit this change directly (and don't have write permissions to slime CVS (ieslick at common-lisp.net).  Is there a proper procedure for testing a change like this if you don't have all the test configurations available locally?

cool. send the patch to the list and i'll apply it if it's good or tell
you what's wrong with it. If it's a big change please supply a ChangeLog
entry (or don't if you don't mind waiting a while for it to get applied).

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen