Skip to content

PreCommandHook: don't lock pack-objects #1675

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.

Sign up for GitHub

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

Merged
derrickstolee merged 1 commit into from
Jun 5, 2020
Merged

PreCommandHook: don't lock pack-objects #1675

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion GVFS/GVFS.Hooks/Program.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,6 +347,7 @@ private static bool ShouldLock(string[] args)
case "merge-base":
case "multi-pack-index":
case "name-rev":
case "pack-objects":
case "push":
case "remote":
case "rev-list":
Expand All @@ -362,7 +363,7 @@ private static bool ShouldLock(string[] args)
return false;

/*
* There are several git commands that are "unsupoorted" in virtualized (VFS4G)
* There are several git commands that are "unsupported" in virtualized (VFS4G)
* enlistments that are blocked by git. Usually, these are blocked before they acquire
* a GVFSLock, but the submodule command is different, and is blocked after acquiring the
* GVFS lock. This can cause issues if another action is attempting to create placeholders.
Expand Down