- #BEST VERSION CONTROL SOFTWARE FOR MAC MANUAL#
- #BEST VERSION CONTROL SOFTWARE FOR MAC PRO#
- #BEST VERSION CONTROL SOFTWARE FOR MAC CODE#
#BEST VERSION CONTROL SOFTWARE FOR MAC CODE#
Google Code then asks you for your login information (which most clients store), and your done. You simply check all the files you want using the very helpful select all option that in my msysgit version wasn't available, type in a commit message, and hit commit. Getting a repository is easy as a checkout, no SSH needed (can't remember if Github required SSH for pulls), and no entire repo + all past commits sitting on your HD.Ĭommitting is extremal easy, mainly because no SSH or staging is required. And since I'm on Windows and have a google account, specifically TortoiseSVN and Google Code.įirst, complete shell integration to do everything on the repository (and for you linux people, RabbitVCS does the same thing), no main GUI needed. The command line junkies around me hated the gui even more.
It locked up on me a few times, had a horrible interface, and CLI-GUI integration was iffy at best. Getting software specific, the base program on Windows is msysgit, which is a terrible interface. (last part is revision number) tells me a lot more than simply 1.8.6 and a note saying that something minor changed, try it
I still remember the marker commits that would pop up saying "Changed version to 1.8.6" or something similar, but you still couldn't do build numbers. Now I know that this is because of the design of git, but any software needs a version number. I rarely could find much help in the docs and simply resorted to google.Īnd with commits, the one thing that I didn't like was the lack of version numbers. Speaking of documentation, at least when I was using it, it seemed everything was in linux man file format, IE confusing and useless to me. The hell does that mean? I should be able to figure out things pretty quickly and not have to consult some weird documentation. You also had the not(!) very helpful commit data.
#BEST VERSION CONTROL SOFTWARE FOR MAC MANUAL#
TMK, I had to first "stage" all the files I wanted to commit (which sucked when you had many many files, took me a while to find the manual command to stage everything), then do the commit, then push to the main repo (why is that a separate operation?!). Then there was the confusing process to make a commit. I will admit that I never worked with anything huge, but I would be afraid to download KDE's repository in Git if the entire repo and its revisions are on my HD. First, I had to generate a ssh private key, paste the public key in Github, then bring up pageant and open my private key each time I wanted to push, which was extremely annoying.Īnd I never really liked that I was pulling down the entire repository. I immediately noticed the amount of work it took to get it to work with Github. When I was interning at a small shop, I was introduced to git on Windows. Why? Because SVN was much easier for a single developer or small team, and git (specifically msysgit) left me with a bad taste in my mouth.
#BEST VERSION CONTROL SOFTWARE FOR MAC PRO#
So this post is a bit out of date with the Pro SVN comments and general anti-DVCS, but the anti-git stuff is still relevant Warning: Since this post I've found Mercurial and love it much better than SVN.
0 kommentar(er)
