{"thread":{"id":"14560","subject":"cygwin git and network drives","startedAt":"2008-07-21T07:09:47Z","lastAt":"2008-07-21T07:09:47Z","messageCount":1,"participants":["Peter Vun"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"84149","messageId":"loom.20080721T065829-347@post.gmane.org","threadId":"14560","inReplyTo":null,"subject":"cygwin git and network drives","fromName":"Peter Vun","fromEmail":"pvun@ics.mq.edu.au","sentAt":"2008-07-21T07:09:47Z","receivedAt":"2008-07-21T07:09:47Z","isPatch":false,"sender":{"key":"pvun@ics.mq.edu.au","avatar":null},"body":"Hi Guys, \n\nI'm currently testing Git on our office network and I noticed on \nthe following site\n\nhttp://git.or.cz/gitwiki/CygwinBinaryInstall\n\nthat is says\n\nUse git on local NTFS disks -- Network drives disks don't support the\nfilesystem semantics GIT needs; for interoperability purposes you \ncan store bare repositories on FAT32 disks.\n\nDoes anyone know if the above statement is still valid? Personally, I've \ntested cygwin Git with network drives a couple of times and I haven't \nencountered any problems, (yet!!). \n\nAny details on Git's limits with regards to this issue would be much\nappreciated. \n\nCheers\nPeter\n"}]}