This stuff sounds good to me. I don't have time to look at it today,
but should in the next few days. It's too bad you didn't coordinate
ahead of time; merging may be a pain as I also made some significant
parser changes.
I haven't heard from Greg Woods in quite a while, but the plan was to
have the XEmacs changes merged back into his official version and have
him resume primary maintainership. I can't even seem to send him
email directly from here as it always bounces. If I send to the
pcl-cvs list, however, it sometimes seems to get through.
I'd really like to resolve maintainership and have a single repository
tracking all the changes. Would you want to have commit access to the
xemacs.org repository and share maintainership with me?
greg
>>>> "SM" == Stefan Monnier
<monnier+lists/cvs/pcl(a)tequila.cs.yale.edu> writes:
SM>
SM> I've been hacking wildly on pcl-cvs these last days and am wondering if
you're
SM> interested in using my changes for the XEmacs tree.
SM> I based my changes on the r1-34 version of the XEmacs cvs tree but have made
SM> substantial changes. I just noticed that you've made some more changes since
SM> then that I haven't merged back into my tree.
SM>
SM> I've posted announcements on the pcl-cvs mailing list and you can go take a
SM> look at
ftp://rum.cs.yale.edu/pub/monnier/pcl-cvs/ for the current head of
SM> my cvs tree.
SM>
SM> Main changes:
SM> - heavy use of CL
SM> - the parser is a set of macros instead of a small interpreter (i.e. edebug
SM> works just fine)
SM> - cvs-execute-list is not used any more (everything goes through run-cvs-process
SM> and most operations also go through the parser)
SM> - ability to have more than one *cvs* buffer
SM> - the parser is moved to pcl-cvs-parse.el
SM> - the fileinfo stuff (and the cvs-states stuff also which is now put to use)
SM> is move to pcl-cvs-info.el
SM> - less code redundancy.
SM>
SM> My changes are substantial enough that it's much easier to merge your changes
SM> into my code than the reverse. Also I develop on FSF Emacs, so some XEmacs
SM> testing of my code would be necessary/welcome.
SM>
SM>
SM> Stefan
SM>