Opened at 2011-08-26T20:01:56Z
Last modified at 2011-09-05T02:05:40Z
#1506 closed defect
mutable-type should imply mutable in tahoe put — at Version 2
Reported by: | kevan | Owned by: | kevan |
---|---|---|---|
Priority: | major | Milestone: | 1.9.0 |
Component: | code-frontend-cli | Version: | 1.9.0a1 |
Keywords: | mutable mdmf tahoe-put usability reviewed | Cc: | |
Launchpad Bug: |
Description (last modified by davidsarah)
Currently, if you do tahoe put --mutable-type=mdmf some_file, an immutable (CHK or LIT) file is created, since tahoe 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.)
Change History (3)
comment:1 Changed at 2011-08-26T20:14:15Z by kevan
- Component changed from unknown to code-frontend-cli
comment:2 Changed at 2011-08-26T20:25:20Z by davidsarah
- Description modified (diff)
- Keywords mutable mdmf tahoe-put usability added
Changed at 2011-09-03T19:10:31Z by kevan
Note: See
TracTickets for help on using
tickets.