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.

Sign up for GitHub

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

Jump to bottom

strict parsing of preservation policy #40

Closed
sbrudenell opened this issue Jul 21, 2024 · 0 comments · Fixed by #47
Closed

strict parsing of preservation policy #40

sbrudenell opened this issue Jul 21, 2024 · 0 comments · Fixed by #47
Assignees
@sbrudenell
Labels
enhancement New feature or request
Milestone
v1.0.0

Comments

@sbrudenell
Copy link
Owner

right now we allow 1y 1m and 1m 1y

I think the outcome of #35 is that it will make more sense for the definitions in the policy to always reflect tree hierarchy.
@sbrudenell sbrudenell added the enhancement New feature or request label Jul 21, 2024
@sbrudenell sbrudenell added this to the v0.1.0 milestone Jul 21, 2024
@sbrudenell sbrudenell self-assigned this Jul 21, 2024
@sbrudenell sbrudenell mentioned this issue Aug 8, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbrudenell sbrudenell

Labels
enhancement New feature or request
Projects
None yet
Milestone
v1.0.0
Development

Successfully merging a pull request may close this issue.

enforce strict order in preservation params sbrudenell/btrfs2s3
1 participant
@sbrudenell