Git

Ed Poore

I doubt it. If it isn't intuitive then we need to fix it. - Chris Maunder

Ed Poore

N a v a n e e t h wrote:

Have you faced any problems with it?

Same thing as mentioned below, slight problems with TortoiseGit but no issues (and loving it) with Git on Linux.

I doubt it. If it isn't intuitive then we need to fix it. - Chris Maunder

John M Drescher

I use .git a lot (almost daily) on linux but not for my code. Branching and merging is great with .git however for programming I find it essential to see arbitrary diffs of individual files (not commits) in the web view. I have not found a satisfactory solution for this with .git or any other distributed scm. [EDIT]BTW, If anyone wants to know what I use .git for that is not code. I have my own repositories of gentoo ebuilds. ebuilds are what the gentoo package manager uses to install packages. http://github.com/drescherjm[^] [/EDIT]

John

modified on Sunday, December 6, 2009 3:06 PM

Chris Austin

I've been using Git and Mercurial for about three years now. Both are great DVCS systems. Lately I've begun playing with Fossil[^] for a smaller project. I like it because it comes with a built in wiki, bug tracking and, comes in a single binary.

And above all things, never think that you're not good enough yourself. A man should never think that. My belief is that in life people will take you at your own reckoning. --Isaac Asimov Avoid the crowd. Do your own thinking independently. Be the chess player, not the chess piece. --Ralph Charell

Nemanja Trifunovic

Last time I looked at it the Windows version was not quite there yet. Is it better now?

utf8-cpp

N a v a n e e t h

Not sure about the windows version. I am on Linux and it works well there.

Best wishes, Navaneeth

N a v a n e e t h

It is very easy to import a SVN repository to Git. The main problem what we were facing was with experimenting new features on our application. We are 32 developers team and many of them wants to do experiments on certain features before they actually implement it. So the usual practice is to create a branch and do the experiment over there and merge back to the development tree once done. But as I said, this merging was not very straightforward and each branch created has to be in repository. When the project size increases, it will be hard to maintain. With Git, branching and merging is trivial. Git will keep the whole repository on the working machine and you don't need server communication to do commits or diffs. This helps to experiment the features, revert back if not satisfied or merge once the changes are done, easily. Once the changes are done, it will be pulled to the main branch which will be shared with everyone. Git makes all these pretty easy.

Best wishes, Navaneeth

peterchen

It's cool if you embrace the command line. TortoiseGIT is ok for most things, but without command line it isn't sufficient. GIT GUI is confusing and ugly and far from intuitive, but has some features that Tortoise doesn't have. The one thing that annoys me is the fixed location of the local repository, residing besides or below the project. I'd love to have it in a location that is included in the normal regular backups, or at least easier to back up for multiple projects. Also, it forces me to have a one-deeper directory structure.

Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server

N a v a n e e t h

I haven't tried the Tortoise Git. I am happy with command line. :)

Best wishes, Navaneeth

malpeli

GIT rocks!..... you should try GitHub too... great community and service... if you signin my user in github is tcha-tcho best regards from brazil!

Dr Luiji

Hi Navaneeth,

N a v a n e e t h wrote:

Getting lot of problems when the development team size is increasing. Its hard to maintain branches and merging is a real pain.

ouch.. what do you mean? I've finished right now to migrate all the code from VSS to SVN... Now I'm using TortoiseSVN and AnkhSVN for the VS2005 project and I decided to use initially the Lock-Modify-Unlock solution to replicate the VSS as possible. All goes fine but I've used it too little to give an opinion. Soon (tomorrow or the day after) everyone here will start to use it. Why you changed SVN?

Dr.Luiji Trust and you'll be trusted. My Blog : The Code Is Art

Fabio Franco

Until now I see no reason to move from SVN. I had no problems with it. We have several branches for several releases. The repository has grown really big. And Tortoise is a life saver. Solving conflits and performin merges are quick and natural. I don't know why you are having problems, maybe you are the unlucky from the crowd. I'm with SVN and don't intend to let it go.