Larry Jones wrote: >Stephen Rasku writes: >> >> I believe what he is refering to is that the more SCCS will get slower the >> more revisions you have in a file. Getting a file from RCS/CVS should be >> a constant time event for the latest version because RCS/CVS stores the >> latest revision verbatim. However, as I understand it, SCCS saves each >> version as "#ifdefs". I don't think it stores a complete copy of the >> latest revision. As such, it will have to calculate what is in the latest >> version and how long this takes will depend on how many revisions you >> have. > >SCCS can retrieve any revision in one pass through the file. As you >say, there are the equivalent of "#ifdefs" that specify which revisions >include the following lines , so there's very little processing time, >it's mostly just I/O time. CVS as currently implemented has to read the >entire RCS file before doing anything, so I'd be very surprised if it's >significantly faster.
Really? Looking at a sample ,v file I can see the latest revision stored intact near the top of the file. I don't know why it would have to read the other revisions. -- Stephen Rasku E-mail: [EMAIL PROTECTED] Senior Software Engineer Web: http://www.pop-star.net/ TGI Technologies _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
