Repository navigation
feat(manifest): a manifest can say its files are held elsewhere - #22
Merged
Merged
Conversation
held: {by, at} names the machine that keeps a manifest's files, and where
to ask it for one. Where the covered directory is present nothing changes.
Where it is not, the rows are held elsewhere rather than missing: check
reports nothing, manifest says who holds them, --verify verifies nothing
and exits non-zero, and --update and --add refuse rather than empty the
record from a directory this device does not have. Without held, an absent
root is a broken link as before.
Workspace::set_manifest_held and manifest --held-by/--held-at/--not-held
set it, rewriting the manifest and re-pinning the node in one change set.
ManifestStatus gains held and elsewhere.
For a photo archive on a NAS whose workspace travels to devices that will
never carry 1.66 TB. Also puts manifests.md section 3's closing paragraphs
back above 3.1, where they belong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
held: {by, at} names the machine that keeps a manifest's files, and where
to ask it for one. Where the covered directory is present nothing changes.
Where it is not, the rows are held elsewhere rather than missing: check
reports nothing, manifest says who holds them, --verify verifies nothing
and exits non-zero, and --update and --add refuse rather than empty the
record from a directory this device does not have. Without held, an absent
root is a broken link as before.
Workspace::set_manifest_held and manifest --held-by/--held-at/--not-held
set it, rewriting the manifest and re-pinning the node in one change set.
ManifestStatus gains held and elsewhere.
For a photo archive on a NAS whose workspace travels to devices that will
never carry 1.66 TB. Also puts manifests.md section 3's closing paragraphs
back above 3.1, where they belong.