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

Make restic find more intuitive by treating --newest as inclusive #3814

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

hyperfekt
Copy link

@hyperfekt hyperfekt commented Jul 3, 2022

What does this PR change? What problem does it solve?

When specifying --newest for restic find, the listed files will not actually include any with the stated modification time, but only those before it, which is not what the common assumption would be. With this PR, any files that have a modification timestamp that is an extension of the given option will be displayed also.

Checklist

  • I have read the contribution guidelines.
  • I have enabled maintainer edits.
  • I have added tests for all code changes.
    No. Unsure how to.
  • I have added documentation for relevant changes (in the manual).
  • There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
  • I have run gofmt on the code in all commits.
  • All commit messages are formatted in the same style as the other commits in the repo.
  • I'm done! This pull request is ready for review.

Given a datetime with a resolution lower than nanoseconds, find will list files
modified up to the last nanosecond of the given datetime instead of the first.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant