CVS usage specification
2 First Update before modifying the file. This means that the version is as new as possible, once a conflict occurs, resolving its workload will be relatively small;
2 timely commits. The smaller the code difference between the local code and the code library, the smaller the difficulty of the merger, and the probability they have a relatively large probability can get a new version);
2 Modify different functional units to Separate. On the one hand, doing this can be possible as early as possible, reducing the difficulty of mergers of others; on the other hand, since CVS provides the ability to retreat to previous versions, once a function modification is made, it is easy to modify the content. , Not the entire modification back to normal code;
2 All code involved in the same feature COMMIT. I don't want to separate the code to code to change the same function, because this will bring trouble to the future tracking;
2 After debugging first. This will reduce others will cause problems caused by synchronizing intermediate results, and even submit conflicts may occur;
2 Write a commit log (submit log). The CVS is allowed to save the Commit log, and you can write this code, and what kind of modification has been made. Clear COMMIT LOG can help other developers understand the modified content without carefully read the code, thereby greatly Improve development efficiency; on the other hand, these logs are very valuable for developers and the entire development team;
2 Regularly keep the client clock consistent with the server clock, set by command "Net Time CVSServer / Set".
2 Do not use UNIX CVS clients (including Cygwin's CVS client) Checkin DOS format file.
