forked from git-for-windows/git
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Sparse Index] Integrate with git status
#374
Merged
derrickstolee
merged 26 commits into
microsoft:features/sparse-index
from
derrickstolee:sparse-index/vfs-status
Jun 21, 2021
Merged
Changes from 9 commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
2a4a725
sparse-index: skip indexes with unmerged entries
derrickstolee f5bae86
sparse-index: include EXTENDED flag when expanding
derrickstolee d965669
t1092: replace incorrect 'echo' with 'cat'
derrickstolee 44a9402
t1092: expand repository data shape
derrickstolee 701ac0e
t1092: add tests for status/add and sparse files
derrickstolee 587333f
unpack-trees: preserve cache_bottom
derrickstolee 6fc898a
unpack-trees: compare sparse directories correctly
derrickstolee b676ef4
unpack-trees: unpack sparse directory entries
derrickstolee d693f00
dir.c: accept a directory as part of cone-mode patterns
derrickstolee ed11cfc
diff-lib: handle index diffs with sparse dirs
derrickstolee 48fd25a
status: skip sparse-checkout percentage with sparse-index
derrickstolee 3499105
status: use sparse-index throughout
derrickstolee 60a6706
wt-status: expand added sparse directory entries
derrickstolee 76bd8ec
fsmonitor: integrate with sparse index
derrickstolee a1a570a
Merge sparse-aware 'git status' into vfs-2.32.0
derrickstolee 093a832
t1092: cleanups
derrickstolee 722e7cd
fixup! unpack-trees: unpack sparse directory entries
derrickstolee 9edbebf
fixup! unpack-trees: unpack sparse directory entries
derrickstolee 0fda21d
fixup! t1092: expand repository data shape
derrickstolee 610518c
fixup! unpack-trees: unpack sparse directory entries
derrickstolee 320586f
fixup! dir.c: accept a directory as part of cone-mode patterns
derrickstolee ddaebb7
fixup! wt-status: expand added sparse directory entries
derrickstolee 44bfb50
fixup! sparse-index: implement ensure_full_index()
derrickstolee 0c20b94
fixup! fsmonitor: integrate with sparse index
derrickstolee f462956
fixup! fixup! t1092: expand repository data shape
derrickstolee 87a3a29
fixup! wt-status: expand added sparse directory entries
derrickstolee 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
This file contains 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 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 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.
Would
.
make sense here instead of-
?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.
For some reason having a filename as
.
seems stranger to me than-
. Perhaps_
would seem less odd?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.
I talked with @dscho offline here and here is the conclusion:
path/to/directory/.
is semantically identical topath/to/directory
, so.
is a natural option here./.
. While it is dumb enough to ignore that, we would be adding an expectation that it remains dumb and otherwise doesn't check that the input path is a valid name for a file.The conclusion is that this is a clever idea, but perhaps too clever.
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.
I'm not sure there is a correct answer here. But it makes me want to say that we want to treat the ce's as a {type,path} tuple with an accessor and all that and get away from the pattern of just iterating over a dumb list of strings (that all callers know is a dumb list of strings).
Is there existing code to detect file -vs- symlink collisions? or file -vs- submodule collisions? How are they handled?
I mean we're adding the concept of (sparse) directory nodes into the index; it would be nice if they collided the same way. (I'm not trying to cause problems, just asking dumb questions.)