-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
remove_dir_all_where does not properly handle recursion #35
Comments
sosthene-nitrokey
added a commit
to sosthene-nitrokey/littlefs2
that referenced
this issue
Apr 12, 2023
sosthene-nitrokey
added a commit
to sosthene-nitrokey/littlefs2
that referenced
this issue
Apr 12, 2023
sosthene-nitrokey
added a commit
to sosthene-nitrokey/littlefs2
that referenced
this issue
Apr 12, 2023
sosthene-nitrokey
added a commit
to sosthene-nitrokey/littlefs2
that referenced
this issue
Apr 19, 2023
sosthene-nitrokey
added a commit
to sosthene-nitrokey/littlefs2
that referenced
this issue
Apr 20, 2023
Fixes trussed-dev#35 `remove_dir_all_where` correctly handles the case where a file in the directory was skipped, but not if a subdirectory was skipped. This commit fixes it
sosthene-nitrokey
added a commit
to sosthene-nitrokey/littlefs2
that referenced
this issue
Apr 20, 2023
Fixes trussed-dev#35 `remove_dir_all_where` correctly handles the case where a file in the directory was skipped, but not if a subdirectory was skipped. This commit fixes it
sosthene-nitrokey
added a commit
that referenced
this issue
Jun 12, 2023
Fixes #35 `remove_dir_all_where` correctly handles the case where a file in the directory was skipped, but not if a subdirectory was skipped. This commit fixes it
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It correctly handles the case where the files are left in the directory, but doesn't handle if a sub-directory was not deleted.
The text was updated successfully, but these errors were encountered: