This repository was archived by the owner on Nov 9, 2017. It is now read-only.
forked from git-for-windows/git
-
Notifications
You must be signed in to change notification settings - Fork 315
Symlink support #172
Merged
Merged
Symlink support #172
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
82cc187
MinGW: Add symlink support for NTFS on windows
frogonwheels 75b8a67
MinGW: Allow passing the symlink target type from index information.
frogonwheels eabcbcc
mingw: Create directory/file symlink from information available
frogonwheels 4d733b9
test: Work around lack of windows native symlink support in current msys
frogonwheels dda0d3d
test: Don't have dangling symlinks in tests (for msys)
frogonwheels 4a83680
test: Factor abspath_of_dir for testing 'absolute paths'
frogonwheels a662ef7
test: Implement mingw abspath_of_dir
frogonwheels 2fa9eca
test: Factor out 'check_symlink' for stash tests
frogonwheels 3259ff9
test: Override 'check_symlink' to work with incomplete mingw
frogonwheels 1919ecf
contrib: make git-new-workdir work with windows symlinks.
frogonwheels 0a77793
test: Differentiate ability for gnu utils to handle symlinks from git
frogonwheels 1930ec6
test: Fixup 3900 i38n quoting
frogonwheels db19ecf
test: Introduce binary compare function
frogonwheels 3e5df5d
test: Fix remote failure test to use correct env variable
frogonwheels File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
git-new-workdir was always meant to use the plain
.git
file feature, i.e. writing a file called.git
with the single linegitdir: <path>
. Given all the problems with reparse points, I am very reluctant to go the route outlined in this diff.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once we have an msys with functional
ln
andtest
commands wrt symlinks, then this can go away. Meanwhile, this is required for the tests to work. git-new-workdir didn't funciton for me without these changes. Is there a rewrite of git-new-workdir somewhere that works without symlinks? If so I'm quite happy to use that.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
git-new-workdir
is incontrib/
, so upstream does not even test it on a regular basis. I would rather not care about it too much in this context, because the (long overdue) rewrite to use thegitfile
feature is completely independent of the issue of using reparse points.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OH, I forgot to mention - git-new-workdir is used by the tests, which is why I need it to work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never mind my comment about using
gitdir:
... it does not work in this case because we cannot share the complete.git/
directory; parts need to be different (and lead to tremendous problems, which is whygit new-workdir
never became part of the official Git).