##// END OF EJS Templates
lfs: ensure the blob is linked to the remote store on skipped uploads...
lfs: ensure the blob is linked to the remote store on skipped uploads I noticed a "missing" blob when pushing two repositories with common blobs to a fresh server, and then running `hg verify` as a user different from the one running the web server. When pushing the second repo, several of the blobs already existed in the user cache, so the server indicated to the client that it doesn't need to upload the blobs. That's good enough for the web server process to serve up in the future. But a different user has a different cache by default, so verify complains that `lfs.url` needs to be set, because it wants to fetch the missing blobs. Aside from that corner case, it's better to keep all of the blobs in the repo whenever possible. Especially since the largefiles wiki says the user cache can be deleted at any time to reclaim disk space- users switching over may have the same expectations.
Matt Harbison -
r39491:a913d289 default
Show More
Name Size Modified Last Commit Author
/ contrib / python-zstandard / zstd / dictBuilder
cover.c Loading ...
divsufsort.c Loading ...
divsufsort.h Loading ...
zdict.c Loading ...
zdict.h Loading ...