Decimating old backups - sparseness option

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
infrastructure

Research direction

Read the discussion in referenced issue #494 first; it is the only context provided for the proposed sparseness option. Clarify the desired old-backup decimation behavior and acceptance criteria with maintainers before locating implementation and tests; done means an agreed, verified sparseness feature.

Written by the indexing model from the issue text.

Description

Feature

Initially reported here https://github.com/meskyanichi/backup/issues/494.
See the referenced issue for a discussion.

Suggestions are welcome!

Dominant language
No language data
Stars
6
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from backup/backup-features

All issues in backup/backup-features

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.