-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul Sander <[EMAIL PROTECTED]> writes:
> There should be little need to parse the output of "cvs log" or "cvs rlog" > if you have access to the server and can run rinfo on the RCS files. It > produces output that's designed to be machine readable. Sources are > located at: > > http://www.wakawaka.com/source.html Thank you for the pointer. I have been aware of rinfo for a number of years, but it is a good thing to remind folks it exists. That said, access to the server for such purposes is not always available. It depends on the nature of the organizations/companies that maintain the cvs repository and how strictly the repository sources are kept as to wether having access to the raw ,v files will be possible for the rinfo command to use. There are also some CVS concepts with regard to 'magic branches' and the dead state that are not really accounted for by the rinfo program (or such is my recollection from a few years ago). If someone were to provide similar functionality into a patch to provide something like a 'cvs info' or 'cvs rinfo' command, I suspect that many folks would find it useful. Thanks, -- Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAYhr53x41pRYZE/gRAk7OAJ9Y6DCN83fCQ9bHI6FW2dOHjDKmUwCcCfFO EkDPG+N8MVoApzt8DVPthxc= =/5wx -----END PGP SIGNATURE----- _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
