mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Discussion of NTFS symlinks, junction points, and reparse points.

Browse source
This commit is contained in:
josh 2012-05-31 20:11:43 +00:00 committed by admin
parent 233d402075
commit c47b1ecda0
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/design/assistant/windows.mdwn
View file

@ -6,6 +6,8 @@ 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.
Currently, on Windows, git checks out symlinks as files containing the symlink
@ -16,3 +18,7 @@ target as their contents.
Lots of ifdefs and pain to deal with POSIX calls in the code base.
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.