Skip to content
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

conflict handling when filestate = BOTH_CHANGED #52

Open
bytinbit opened this issue Sep 10, 2018 · 2 comments
Open

conflict handling when filestate = BOTH_CHANGED #52

bytinbit opened this issue Sep 10, 2018 · 2 comments

Comments

@bytinbit
Copy link
Collaborator

When BOTH files individually changed, we currently override the local file, but this can and should
later be handled as a user decision.

Implementation in settings with override / ignore / ask every time / rename

@bytinbit
Copy link
Collaborator Author

we agree: the simplest implementation is to just rename the local file and download the remote changed file anyway.

another issue has been opened to cover a "second stage": the user can determine in the config what should be done when both (remote, local) have changed.

@The-Compiler
Copy link
Collaborator

@bytinbit started some work on this in the filecache-both-changed branch. Some tests are still missing (we wanted some more fine-grained tests for the logic in syncing.py with the different file states), but otherwise it should be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants