Re: what versioning system do you recommend?
Re: what versioning system do you recommend?
- Subject: Re: what versioning system do you recommend?
- From: Mark Suman <email@hidden>
- Date: Tue, 19 Jan 2010 07:20:20 -0700
I used to only use svn on the command-line, but have recently moved over to git and am pretty happy so far. At work we migrated to a git/gerrit system. Gerrit is a code review tool written by Google that integrates with git. It allows you to push changes and assign someone else on the team to review them. Using the web interface (or cli), they review the changes, make comments, and approve/disapprove the changes. It is a convenient way to insert code reviews as a prominent step in your workflow. (But yes, you may self-approve changes as well, so gerrit doesn't hold you back if you don't want it to.)
To answer the original poster's question:
If you are new to versioning systems, I would say start with subversion. It is a simpler concept to wrap your head around. The learning curve will get out of your way as you work on your project. If you are feeling more gutsy, go with mercurial or git. Don't use cvs.
Mark
On Tue, Jan 19, 2010 at 4:05 AM, Aaron Burghardt
<email@hidden> wrote:
On Jan 18, 2010, at 11:55 PM, Jens Alfke wrote:
A lot of the cool kids seem to be using git these days. I'm not sure what the learning curve would be like compared to subversion; I learned on CVS, so subversion was a natural progression. Git does some things very different that CVS or subversion.
Part of the reason I prefer Mercurial is that it feels a lot like Subversion (and CVS), with a similar command set and metaphor, albeit with extra stuff added to deal with its git-like distributed nature. Whereas git is very idiosyncratic, both in the command syntax and in the workflow itself. I've been using git daily for a few months now and I still have to dig through my O'Reilly book to remember how to do things like revert local changes to a file (because I can't just say "git revert" the way I could with Mercurial or SVN.)
I'm not familiar with the O'Reilly book, but after wading through a number of on-line documents and resources, I found "Pro Git" about the time it was published last July. I find it much clearer with better visuals than anything else I have read, and you can read it on-line:
You're example is tough because "revert" is already in use, but for other cases you can define aliases to make commands more memorable. There are some useful examples in the "Tips and Tricks" section:
I used Subversion for years, but got frustrated with the poor support for merging and the fact that I couldn't access our repository off-line for history and making commits (our repository is required to be on a closed network). After learning Git, I completely agree with Linus that distributed VCS is a better model, so I suggest comparing Subversion to at least one DVCS (not necessarily Git).
Aaron
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden