-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: > That's one place where CVS has deviated from the "golden" > path set by RCS -- RCS is very careful to always work with > revision numbers as strings rather than converting back > and forth between strings and integers, so it never has > such problems. CVS was not as carefully implemented. > Fixing it would be a worthwile goal.
Hmmm... well, in theory, yes. But in practice, I think there are much more likely bugs and features to address first. Are there repositories out there where the revision number is likely to exceed INT_MAX? I know not everyone's using an OS where INT_MAX is 2147483647 or greater, but even so, has anyone even approached 32,000 revisions on a branch yet? Out of curiosity, has anyone tested what happens if the revision numbers roll over? - -- 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 iD8DBQFEaIqDLdDyDwyJw+MRAh7CAKDKWx/YlLSRtAKv+CcPnExXahiQYwCgwwX5 HHtZRp/UnhmmHlZymVjotAI= =BWL9 -----END PGP SIGNATURE----- _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
