-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alexander Taler wrote: > >>>>>>> "Jim" == Jim Hyslop <[EMAIL PROTECTED]> writes: > Jim> BTW, any chance the portion of the code that does this could be > Jim> refactored out into a separate script that can be put into the contrib/ > Jim> directory? > > Not efficiently. It's written on top of the LibCVS objects which > present a very different view of the contents of the cvs > repository than a raw cvs log output. Oh, well. I wouldn't think it would be too difficult to write a separate script.
> While we're on this topic, the real problem with determining tag > date is that tags can be moved or can be applied to a working > directory where everything isn't properly up-to-date. For non-branch tags, yes that's a problem, but for branch tags the timestamp of the branch point and of the first revision on the branch are very difficult to modify manually, so I think you can be fairly confident that the window will be accurate. Actually, when you get down to it, the real problem is CVS's lack of control over metadata, but that's already been rehashed many times. - -- Jim Hyslop Dreampossible: Better software. Simply. http://www.dreampossible.ca Consulting * Mentoring * Training in C/C++ * OOD * SW Development & Practices * Version Management -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDou/VLdDyDwyJw+MRAjNOAJ9H8bNuodrY2Ujhr8DNPSg9Gqj2oQCg2xWD 5Ws424clzOV9AD0hCeoT5hQ= =qo3C -----END PGP SIGNATURE----- _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
