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 Initial Version
| 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
Currently, if you do tahoe put --mutable-type=mdmf some_file, a CHK file is created, since tahoe put only pays attention to the mutable-type argument if the mutable argument 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)
Note: See
TracTickets for help on using
tickets.
