diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-05-31 19:50:46 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-05-31 19:50:46 -0400 |
| commit | d4a95faeb2786027e13cc3f49825a6b4ad231768 (patch) | |
| tree | f3467f9231aa68f26643b6480bc0187aaa62164e | |
| parent | 3a10095d40cf9a9e0380b6b10e1ebe304f1537c0 (diff) | |
| parent | c47b1ecda00cea6d9922e0733c3ab365bc2f004d (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
| -rw-r--r-- | doc/design/assistant/windows.mdwn | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/doc/design/assistant/windows.mdwn b/doc/design/assistant/windows.mdwn index 0b176934b..da669ad82 100644 --- a/doc/design/assistant/windows.mdwn +++ b/doc/design/assistant/windows.mdwn @@ -6,12 +6,19 @@ Apparently new versions of Windows have something very like symlinks. (Or really, 3 or so things not entirely unlike symlinks and all different.) Stackoverflow has some details. +NTFS supports symbolic links two different ways: an [[!wikipedia NTFS symbolic link]] and an [[!wikipedia NTFS_junction_point]]. The former seems like the closest analogue to POSIX symlinks. + Make git use them, as it (apparently) does not yet. -(What **does** git do on Windows when it clones a repo with symlinks?) +Currently, on Windows, git checks out symlinks as files containing the symlink +target as their contents. ## POSIX Lots of ifdefs and pain to deal with POSIX calls in the code base. -Or I could try to use Cywin. +Or I could try to use Cygwin. + +## Deeper system integration + +[NTFS Reparse Points](http://msdn.microsoft.com/en-us/library/aa365503%28v=VS.85%29.aspx) allow a program to define how the OS will interpret a file or directory in arbitrary ways. This requires writing a file system filter. |