mutable-type should imply mutable in tahoe put #1506
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1506
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, if you do
tahoe put --mutable-type=mdmf some_file
, an immutable (CHK or LIT) file is created, sincetahoe put
only pays attention to the--mutable-type
option if the--mutable
option is also given. This is surprising; we should treat--mutable-type
as implying--mutable
. Then--mutable
can be understood to mean "upload a mutable file using whatever the default mutable type is", and--mutable-type
can be understood as a way to override that default.(This improvement was suggested by davidsarah in #393, comment 141.)
Attachment fix-mutable-type.darcspatch (9622 bytes) added
fix-mutable-type.darcspatch includes a test for this issue and a fix that makes the test pass.
Reviewed and manually smoke-tested, +1.
Applied in changeset:64996a913d014b5f.