-
Notifications
You must be signed in to change notification settings - Fork 7
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
Preserve mtime, etag #83
Comments
Questions:
|
@come-nc good points. for the mtime, we can use `touch()' as in #84 the instance will behave fine. regarding bogus mtimes, I'd assume that instances that have them are already fixed by now. |
for etag, it's a different discussion which I'm afraid will be much more complicated |
I don't think we should preserve etags because of the above reason. mtime preservation has been merged, closing |
Preserve more file metadata like mtime and etag.
Not preserving leads to apps like recommendations thinking that all files are new and then recommends them all.
This is also important in case the user has local data and they simply reconfigure their desktop client to point at the new account and keep the local data. I believe that having a different mtime would cause the desktop client to redownload all files while having the same mtime would keep them. (I was able to keep the local files with a new account yesterday, that's how I know!)
The text was updated successfully, but these errors were encountered: