-
Notifications
You must be signed in to change notification settings - Fork 98
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
multi-pack-index expire doesn't do anything if --objects-dir contains backward slashes #497
Comments
Thanks, @nikola-sh. I've confirmed that VFS for Git sends the path in the format you are describing AND that the The root cause is an upstream change in how we found the existing multi-pack-index from the given This bug only affects VFS for Git. Scalar uses Git's background maintenance, which passes the paths in the Unix style already. I'll send a fix into |
…t-dir This resolves #497. Looking at this, it seems that VFS for Git users have not been getting all of the benefits of background maintenance for quite some time. This will probably justify a `v2.36.0.vfs.0.1` release for those users. We should wait for upstream feedback, first. I will prepare an upstream patch soon.
…t-dir This resolves #497. Looking at this, it seems that VFS for Git users have not been getting all of the benefits of background maintenance for quite some time. This will probably justify a `v2.36.0.vfs.0.1` release for those users. We should wait for upstream feedback, first. I will prepare an upstream patch soon.
…t-dir This resolves #497. Looking at this, it seems that VFS for Git users have not been getting all of the benefits of background maintenance for quite some time. This will probably justify a `v2.36.0.vfs.0.1` release for those users. We should wait for upstream feedback, first. I will prepare an upstream patch soon.
…t-dir This resolves #497. Looking at this, it seems that VFS for Git users have not been getting all of the benefits of background maintenance for quite some time. This will probably justify a `v2.36.0.vfs.0.1` release for those users. We should wait for upstream feedback, first. I will prepare an upstream patch soon.
VFSForGit runs
PackfileMaintenanceStep
periodically, but content ofpack
subdirectory in.gvfsCache
remains unchanged.The reason is that
git multi-pack-index expire
command doesn't work with backward slash paths for--object-dir
(see reproduction example below).So VFSForGit runs
expire
with backward slashes and it doesn't do anything.It seems git behavior should not depend on paths format.
or closed issue matching
what I'm seeing, including in the
git-for-windows/git
tracker.Setup
microsoft/git
are you using? Is it 32-bit or 64-bit?Are you using Scalar or VFS for Git?
VFS for Git
If VFS for Git, then what version?
to the issue you're seeing?
no
Details
CMD
Minimal, Complete, and Verifiable example
this will help us understand the issue.
If you run
multi-pack-index expire
with backward slashes for--object-dir
command do nothingCommand starts doing smth with forward slashes for
--object-dir
:If the problem was occurring with a specific repository, can you specify
the repository?
The text was updated successfully, but these errors were encountered: