I think I now understand why "write a script" was the right answer to my problem and why it will work, but now that I've started thinking about CVS, I realize I really do need to know more about it, so I -will- be taking advantage of your links. Thanks for your generous assistance -----Original Message----- From: Randall R Schulz [SMTP:[EMAIL PROTECTED]] Sent: Thursday, June 28, 2001 1:20 PM To: [EMAIL PROTECTED] Subject: CVS Protocol Documentation Steve, I did some digging in an attempt to find the CVS protocol specification. I discovered that it's kept with the sources, not separately in the download areas as is the PDF document I downloaded today (so I'll have something more up-to-date than the 1.9 printed edition I have on my bookshelf). According to this page, <http://www.cvshome.org/cyclic/cvs/dev-res.html>, the protocol specification is in a TeX file "doc/cvsclient.texi" within the source tree. Your Linux system should have the tools for turning this into something readable, whether PostScript or just formatted ASCII. Look under the heading "CVS Client/server protocol." I think this page will interest you in its own right--it starts out like this "We like to see people working on CVS or software that works together with CVS." There's other stuff there that will probably be helpful to you. Randy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
