Marek Baczynski wrote:
While UNC paths of \\server\resource\path kind don't work, mapped
drives seem to work fine (I was able to pull from and push to a repo
on such drive.)
I did, sorta kinda, get that to work. Even there I had a bit of trouble
though. Sorry I can't be more specific, but I'm at my home computer now
so there's no good way to refresh my memory.
Even so, telling everyone something like "always map \\soandso\foo\bar
to the letter Q so all our scripts work on your rig" seems kinda cheesey
to me. With the "git://" protocol we can at least publish universal
addresses and expect it to work the same for everyone. Anyway, "git://"
worked great once I got the cygwin git-daemon setup correctly.
Another thing is at work we tend to put the master project repositories
on the equipment before we ship it to the customer site, and keep local
repositories that we periodically update from the remote masters after
ship. There are literally hundreds of these things out there, all over
the world. (I think you can see the attraction of Git for me). I'm sure
Windows has a way to handle that many drives, but I don't like the idea
of trying to remember if job 8592 was on drive AABA or on drive ABAA. :-)
--
T.E.D. Home - mailto:[EMAIL PROTECTED]
Homepage - http://www.telepath.com/~dennison/Ted/TED.html
--
We'll have to have dinner out; the toaster's broken.
