>>>> Ideally we'd prefer to simply create our remote repository on a >>>> drive of one of our local network servers. Is this possible? >>> >>> Yes, this is possible, but it's not advised to keep such a >>> "reference" repository on an exported networked drive for a number >>> of reasons (both performance and bug-free operation). >> >> I agree that performance is not ideal (although if you are on a fast >> LAN, it probably would not matter much), but I do not recall any >> specific bugs in that area. Can you elaborate? > > This one [1] for instance. I also recall seing people having other > "mystical" problems with setups like this so I somehow developed an idea > than having a repository on a networked drive is asking for troubles. > Of course, if there are happy users of such setups, I would be glad to > hear as my precautions might well be unfounded for the recent versions > of Git. > > 1. http://code.google.com/p/msysgit/issues/detail?id=130
A group I was with used a master repository on a windows share for quite some time without a database corruption being seen. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
