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

Add debugging for issue #338 - recursive deletion fails when retention policy is enabled #341

Merged
merged 3 commits into from
Jan 19, 2019

Conversation

abraunegg
Copy link
Owner

* Add debugging for issue #338
@abraunegg abraunegg changed the title Add debugging for issue #338 Add debugging for issue #338 - recursive deletion fails when retention policy is enabled Jan 11, 2019
norbusan
norbusan previously approved these changes Jan 16, 2019
Copy link
Collaborator

@norbusan norbusan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine, compiles.

src/sync.d Show resolved Hide resolved
@abraunegg abraunegg merged commit 83cc2e4 into master Jan 19, 2019
@abraunegg abraunegg deleted the issue-#338 branch January 21, 2019 20:08
@lock
Copy link

lock bot commented Feb 20, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 20, 2019
darrenedale pushed a commit to darrenedale/onedrive that referenced this pull request Aug 4, 2022
* Resolve where '--single-directory' is used to sync a single directory,
but a file / folder is 'moved' on OneDrive to outside the scope of the
focus of the '--single-directory' path. Before this change, the file
would remain in the local path (original location) whilst it would
reside in the new OneDrive path. This patch looks for this mis match and
deletes the local file / folder to reflect it is no longer in the same
OneDrive path.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants