Proudly hosted by Linux Tech Networks
Can't find what you're looking for? Check out our Linux Discussion Forums or you can use the form below
CVS Best Practices
| Revision History |
|---|
| Revision 0.7 | 2005-10-15 | Revised by: vv |
| A bunch of minor fixes as suggested by readers. |
| Revision 0.6 | 2002-09-10 | Revised by: vv |
| Added content related to tagging and daily builds. Changed
Linuxdoc URLs to tldp. Fixed stale links and added other corrections
suggested by readers. |
| Revision 0.5 | 2002-08-25 | Revised by: vv |
| Fixed some more errors in the document and added references to
other CVS sources and some server side scripting |
| Revision 0.4 | 2002-03-10 | Revised by: vv |
| Added new email address, Added an example flow to show how the
practices help |
| Revision 0.3 | 2001-12-06 | Revised by: vv |
| Grammatical errors cleanup |
| Revision 0.2 | 2001-11-27 | Revised by: vv |
| Incorporated first round of feedback and
some minor fixes |
| Revision 0.1 | 2001-11-20 | Revised by: vv |
| Created |
This article explores some of the best practices that can be adopted
while using CVS as the configuration management tool in your software
projects.