11–20 of 27 posts
Do the devs already know git, or will it be a new experience for them? No matter what tool(s) you use, learning to use git effectively will be the hardest part. I use TortoiseGit integrated into Windows Explorer for most stuff, and drop down to the command line in the odd situation where it's needed. I can't give much feedback about the server side, I'm using GitHub.
I use msysgit daily on Windows 7 against a github account. For the most part things work fine but there are a few things that annoy me: - Disagreements about case insensitive paths sometimes confuse git. Renaming a folder simply to change its case is the most common one that catches me. - I run everything through the bash shell which works fine but is a pain to connect to Windows batch files. This makes automation ha…
Using the windows CMD shell works fine.
Git comes with its own SSH that works different to other SSH implementations. I've had problems where Git is earlier in the path, so its SSH was overriding the one I wanted. This broke cwRsync until I worked it out.
The initial import took a ridiculous amount of time (so I did it on a mac eventually), but from that point on I've been flying. The only itchy bit so far is the autocrlf part.
I've found "gitk" and "git gui" good as well. You might find them more than merely adequate. I've used Tortoise with svn, but not with git, so dunno about that, but I'd recommend git gui without hesitation.
I use msysgit daily on Windows 7 against a github account. For the most part things work fine but there are a few things that annoy me: - Disagreements about case insensitive paths sometimes confuse git. Renaming a folder simply to change its case is the most common one that catches me. - I run everything through the bash shell which works fine but is a pain to connect to Windows batch files. This makes automation ha…
> - I run everything through the bash shell which works fine but is a pain to connect to Windows batch files. This makes automation harder than required. What are you using bash or batch files for? Have you tried PowerShell as a replacement for batch files?
I actually have a C# console app as my build script because I can write things there so much faster than anywhere else. It makes calls to Windows and the occasional batch / bash script.
I use msysgit daily on Windows 7 against a github account. For the most part things work fine but there are a few things that annoy me: - Disagreements about case insensitive paths sometimes confuse git. Renaming a folder simply to change its case is the most common one that catches me. - I run everything through the bash shell which works fine but is a pain to connect to Windows batch files. This makes automation ha…
I've used Git on Windows for over a year. msysgit is great, once you've worked out the line endings (the installation asks you for this setting) Using the windows CMD shell works fine. Git comes with its own SSH that works different to other SSH implementations. I've had problems where Git is earlier in the path, so its SSH was overriding the one I wanted. This broke cwRsync until I worked it out.
Do the devs already know git, or will it be a new experience for them? No matter what tool(s) you use, learning to use git effectively will be the hardest part. I use TortoiseGit integrated into Windows Explorer for most stuff, and drop down to the command line in the odd situation where it's needed. I can't give much feedback about the server side, I'm using GitHub.
Do the devs already know git, or will it be a new experience for them? No matter what tool(s) you use, learning to use git effectively will be the hardest part. I use TortoiseGit integrated into Windows Explorer for most stuff, and drop down to the command line in the odd situation where it's needed. I can't give much feedback about the server side, I'm using GitHub.
I am pleased to see TortoiseGit, does it have any big issues? I remember hearing about it a while ago being very "beta" software.
Avoid cygwin git; it appears to work at first, but it gets very slow when you deal with large repositories.
None of the end-to-end GUIs I've used (I've tried about 5) do a respectable job. They all try to layer a svn-style view on top of git. Which is, of course, nothing like svn. Have them watch http://blip.tv/file/4094854, then offer to hold their hand while they get used to the command line. It's worth it. When you really need to click on things, git gui and gitk do the job fine.
Manageable is the most I can say though. I've come to the conclusion that going through the trouble of msysgit/cygwin is not worth it. I don't know if it's an option for you but have you considered other DVCS? From what I heard Mercurial is pretty good on Windows and you'd get pretty much the same advantages as with Git. Others might be able to tell you more about it.
I wouldn't go back to SVN on any platform though - I got addicted to local branches and the speed of having the whole repo locally.