Jan> Ben Wing <ben(a)666.com&gt; writes: >> [2] the xemacs vc is quite Jan> divergent with the fsf's. it is based on a much >> earlier Jan> vc but has a bunch of improvements. i'm not quite sure what Jan> they are. >> for this reason, people haven't thrown out the Jan> xemacs vc and replaced it with >> fsf. Jan> This is wrong. We (Steve and later me) did the throw out Jan> thing in XEmacs 20.3 (The old version is in the vc-cc Jan> package). I have intentionally kept our version as close to Jan> the FSF version as possible. In addition all the differences Jan> are clearly marked as such in the code. Jan> When contacted about merging our stuff back in Andre Spiegel, Jan> the FSF maintainer, said he is currently rewriting vc.el from Jan> scratch to be more modular and at that moment (11/1999) it Jan> would be a waste of effort to merge our stuff in (he did Jan> merge Kyrills NT fixes). He promised to contact me near the Jan> end so we could make a version that worked on both Jan> Emacsen. At that point it should also be much easier to add Jan> clear-case support back in. This sounds good! Do you know Rod Whitby and/or his recent work in http://rwhitby.hplx.net/vc-clearcase.html ? The ClearCase support in that version works fine in native NT XEmacs. Are you still waiting for Andre Spiegel to get back to you? Would it be a bad idea if I tried merging http://rwhitby.hplx.net/vc-clearcase.html into emacs-20.6/lisp/vc*.el? Do you know whether FSF/Andre would refuse to incorporate ClearCase support into their version? Will the vc-cc package become obsolete once the vc package is merged with latest GNU Emacs's vc and clearcase support is added? Best regards, Adrian Jan> Because of this I have refrained from active work on our vc.el and Jan> major syncing. However everything apart from cvs-annotate the more Jan> advanced stuff in cvs-dired should work. Jan> Jan