From aad81425ee5a3b2657646fe98acdc3fce35f9678 Mon Sep 17 00:00:00 2001 From: "http://nullroute.eu.org/~grawity/" Date: Fri, 15 Feb 2013 00:38:01 +0000 Subject: Added a comment --- .../comment_1_32a296fce23ae4b1e18bd5a9964bf619._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/design/assistant/blog/day_188__crippled_filesystem_support/comment_1_32a296fce23ae4b1e18bd5a9964bf619._comment (limited to 'doc/design') diff --git a/doc/design/assistant/blog/day_188__crippled_filesystem_support/comment_1_32a296fce23ae4b1e18bd5a9964bf619._comment b/doc/design/assistant/blog/day_188__crippled_filesystem_support/comment_1_32a296fce23ae4b1e18bd5a9964bf619._comment new file mode 100644 index 000000000..2796964e0 --- /dev/null +++ b/doc/design/assistant/blog/day_188__crippled_filesystem_support/comment_1_32a296fce23ae4b1e18bd5a9964bf619._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="http://nullroute.eu.org/~grawity/" + nickname="Mantas" + subject="comment 1" + date="2013-02-15T00:38:00Z" + content=""" +Windows supports hardlinks on NTFS filesystems. Not sure about the privileges needed; I think all users can create them. + +Recent versions also support symlinks, but that's limited to Administrators by default, so Cygwin-Git (like the rest of Cygwin) uses special files with the \"system\" flag. + +As far as I know, Git does not try to dereference symlinks when merging – it only tracks the paths they point to. Where symlinks are not supported (e.g. vfat filesystems in general, or msysGit on Windows) it simply creates regular files containing the target path (i.e. the raw contents of the respective blobs). + +Regarding the use of Unix permissions: The \"open file\" syscall on Windows has a \"share mode\" flag, which can be used to disallow other programs from opening the file for writing (and/or even reading) as long as git-annex keeps it open. (I guess this is similar to mandatory locks in Linux.) +"""]] -- cgit v1.2.3