-
Notifications
You must be signed in to change notification settings - Fork 63
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
Create a transport layer to use the gvfs protocol #7
Comments
Alternatively, we could investigate a new transport layer for git rather than tinkering with the read-object hook, which is the direction @jeffhostetler is investigating now. |
Labeling this issue as stale. There has been no activity for 30 days. Remove stale label or comment or this issue will be closed in 7 days. |
Labeling this issue as stale. There has been no activity for 30 days. Remove stale label or comment or this issue will be closed in 7 days. |
This is covered by: microsoft/git#191 |
marking closed. |
…ject hook See microsoft/git#191 for the Git code regarding the GVFS transport layer. This can work in tandem with the read-object hook, but it _should_ make the read-object hook irrelevant. * Delete all references to the read-object hook in the product code. This unblocks #4 and the [Mount Removal] tasks #15, #132, #133, #135, #136, and possible others. * Delete the Sparse Verb in favor of `git sparse-checkout set`. * Delete the `BlobPrefetcher` and all references to `--files` or `--folders` prefetching. Resolves #6, #7, #36.
We'll want to gather objects in bulk before a workdir changing operation like checkout.
The text was updated successfully, but these errors were encountered: