rules.txt

cygwin, 著名的在win32下模拟unix操作系统的东东

Rules
To make things run smoothly there are some simple rules that everyone must obey: 

1. All work is performed on a unique and focused branches. If you find that you need other unrelated changes then create another branch for that, and merge it into the branch requiring it. 
2. Never commit anything directly in HEAD. If you do so then the wrath of chriss will befall you.
3. Projects and their CVS branches should be documented in the projects.txt file on the HEAD branch (exception to make rule 2 a rule).
4. A shared branch should be named according to the project or task it is for. 
Private branches or version tags should be prefixed with a user-unique prefix. The user-unique prefix (if different from the username) should also be documented in the projects.txt file. You have no obligation to document your private branches more than this (unless you want to of course, but then it should probably become a shared branch instead...) 
5. Temporary tags should be named Z_username/branchname_tagname (- may be used instead of _). This is to have them away from the normal (useful) branch tags. 
6. Do not commit things on other users private branches, or make extensive changes to a shared branch without first asking the individual responsible for that branch. 
7. Be warned that the log message of ANY commits are sent to the public cygwin-cvs mailinglist, so write intelligent log messages even if it is on a private branch to save your self from the embarrasement. 
8. Use common sense