Sitaram, This might seem a bit off-topic, but I was equally dismayed that git daemon doesn't run under Windows.
What was my solution, at least until it *does* work for Windows? (I confess that this "solution" is just an interim thing, and may fly a bit against the spirit of the msysgit project.) I installed the now open-source VirtualBox on a Windows 2003 server. I used the "Git Server" rPath appliance<http://www.vmware.com/appliances/directory/967>(VMware virtual appliance version). VirtualBox allows you to forward ports between the virtual machine and the physical machine, so I made sure that port 9418 was set up to do so. (I tried but did not succeed getting VirtualBox to run as a Windows service, but you could download the free-as-in-beer VMWare Server to do so.) My solution isn't perfect, but now I fully understand what people are talking about when they say git is fast. Boy is it ever! The Linux daemon (running in a virtual machine) blows away Subversion and of *course*completely decimates SourceSafe in terms of performance. So I'm going to use my virtual daemon until such as time as the msysgit Windows daemon is working. If you're interested, I could forward you configuration information needed to get VirtualBox and my git daemon up and running. - Jim On Tue, Apr 29, 2008 at 9:38 PM, Sitaram Chamarty <[EMAIL PROTECTED]> wrote: > > On Wed, Apr 30, 2008 at 12:25 AM, Johannes Sixt > <[EMAIL PROTECTED]> wrote: > > On Tuesday 29 April 2008 06:18, Sitaram Chamarty wrote: > > There's a patch that makes it work, but only for one connection, which > is > > likely not what you need. > > not really, and I'm trying to evangelise git in a traditional dev shop > which knows (or thinks it knows anyway!) only VSS and perhaps a little > CVS, plus of course the usual perforce and clearcase for large > customers who can pay. So, the more "stable" something is, the > happier I will be in the long term. > > > (1) As long as your repository on G: is bare, you should be fine. This > is how > > I provide access to repositories, and I'd recommend it to you, too. It > is > > discouraged to have the *working directory* on SMBFS because the huge > number > > of stat() calls during regular git usage make a bad user experience. > > Great -- thanks! I didn't realise this distinction. Makes sense, and > is very good to knw. > > > (2) If you go for cygwin, you could do so only on the server and run > > git-daemon under cygwin, but still use msysgit on the clients. > > This is exactly what I finally decided to do, after experimenting with > all the options. Sadly, it still means that dev-to-dev push/pull > won't work (they'd have to go through the central server), but it was > either that or have everyone install cygwin rather than msysgit. > > If I can bother you guys with one more question: how do you do the > "git GUI here" and "git BASH here" stuff when you right click on a > directory in Windows? That's so cool, and the cygwin stuff doesn't > have it...! >
