Revision Control System of the Year
In your opinion, what is the best Revision Control System?
--jeremy |
Having practical experience of cvs,svn,bzr,git and hg.... hg is by far the winner.
|
Quote:
|
I am still using RCS. It is a revision control sysTem good for one to four person projects for those who do not have a lot of time to learn one. I use it to RCS my python code and also my larticles in LaTeX. Its advantage is not features, but simplicity.
|
Git is the only revision control system.
|
I had to use git for few projects, and when I learned it I started to use it for all my documents, including OpenDocument or MSOffice - now I am happy :) No more files with dates as suffix :)
Perhaps other can also be configured to do this, though. |
Quote:
Actually, I'd still go with hg (Mercurial) for that use. You only need the advanced branchy mergy distributed stuff if you need it... it keeps out of your way if you don't. |
Quote:
|
the one I use happens to be git, so I'm voting for it. But I do admit that I'm voting a little unfairly, since I have not evaluated any other version control systems.
|
Quote:
If your changes hit say a file and a header file.... and simply don't work unless you roll _both_ forward or _both_ back.... Then something that understands changesets on a group of files becomes _much_ simpler to use. And that is where mercurial wins. It is simply a database of changesets. |
Git is the best.
It has many commands to do work. But it lacks resuming cloning which is a negative point! |
git, not only because it is so fast, but also because it has interfaces to most other VCS's
and of course github (where is SCCS in the list? :)) |
git, it's what I use the most often.
|
By all means GIT.....GIT ROCKSS \¬¬/
|
git
|
All times are GMT -5. The time now is 04:12 PM. |