| Version Control 101 With CVS | |
By Rodney Amato |
Published
06/20/2006
|
Programming , Web Design , Web Technologies
|
Rating:
![]() ![]() ![]() ![]()
|
|
|
CVS BenefitsCVS lets you do some cool things like working on multiple copies of the same thing, which could be handy if you were working on something like getting a site functioning with different web servers and needed to install a copy for each web server. Using CVS, you can make changes to each copy, and, provided the parts that you are changing arn't in the same part of the same file in both directories, you can do a “CVS Update” to merge the changes from one into the other and visa versa (after commiting them of course). You can even do this with different parts of the same file. ![]() Another handy feature is being able to view the changes you have made since the version in the repository before commiting the change. This lets you pick up things like debugging code before it gets saved in the repository, helping you to keep a cleaner code base and if you do find some code in there that shouldn't be, you can use the annotate feature to work out when it was put in (and who to blame). ![]() |
|
» Home
» Programming
» Version Control 101 With CVS
» Home » Web Design » Version Control 101 With CVS
» Home » Web Technologies » Version Control 101 With CVS
» Home » Web Design » Version Control 101 With CVS
» Home » Web Technologies » Version Control 101 With CVS
or 02-9262-7770 




