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...!
