Hi Bernward, [email protected] wrote on Sat, Jan 12, 2019 at 06:50:29PM +0100:
> Synopsis: some revisions < 1.0 become inaccessible after ci r1.1 > Description: > Revisions r0.1, r0.2 ??? are accessible, > as long as no revison 1.1 or higher is checked in. > After check in of revision 1.1, only the revisions 1.1 and 0.1 > are accessible. A try to check out revison 0.2 gives a message, > that revision 1.1 will be checked out and actually rcs does so. As far as i know, RCS and CVS revision numbers are defined as strings of dot-separated positive non-zero decimal integers, so if revision numbers like "0.1" or "1.0" partially work in some respects, that seems an accident to me and not intentional. So i wouldn't call this a bug in the code. At worst, it might be a documentation issue. Then again, rcs(1) already says: $ mkdir RCS $ ci foo.c This command creates an RCS file foo.c,v in the RCS directory, stores foo.c into it as revision 1.1, and deletes foo.c. And ci(1) already says: Revision numbering starts at 1.1 and increases logically. So i'm not even convinced that the documenation is defective. Yours, Ingo
