|
|
Back to UserFriendly Strip Comments Index
|
Revision control | by KrakensDen | 2005-03-22 19:49:50 |
| Version control is _never_ overkill. |
by Avium |
2005-03-22 20:58:37 |
Even when there is only one developer. There are times when being able to roll back to a previous build is unbelievably useful. And that's not counting keeping multiple machines in sync (laptop and desktop?).
Now, as for what one, there are only two free ones that I can think of that have Windows clients, Subversion and CVS. CVS has been around longer but has some downsides that I just don't like. Like the fact that the file name is used as the tag. Sounds fine until you move all of the functions into another file then want to delete the original...but can't since all of the version information is tied to that filename.
Yes, I have done this. I had a database access class that eventually was split into two classes for a number of very good reasons. Well, now I have to keep an empty file around just to keep the revision info. Okay, so the file's not completely empty. I believe it has a nasty comment about CVS in it. :-D
While I haven't had the time to play with Subversion, it was designed to replace CVS and "fix" all of CVS's issues. Like the networking is designed in there from the start not grafted on at a later date, commits are atomic (ie: no partial commits, it's all or nothing), and the tags are not based on filename. |
|
[ Reply ] |
|
|
[Todays Cartoon Discussion]
[News Index]
|
|