Opened at 2011-08-26T20:01:56Z

Closed at 2011-09-05T02:05:40Z

#1506 closed defect (fixed)

mutable-type should imply mutable in tahoe put

Reported by: kevan Owned by:
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.)

Attachments (1)

fix-mutable-type.darcspatch​ (9.4 KB) - added by kevan at 2011-09-03T19:10:31Z.

Download all attachments as: .zip

Change History (6)

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

comment:3 Changed at 2011-09-03T19:15:51Z by kevan

  • Keywords review-needed added
  • Owner kevan deleted

attachment:fix-mutable-type.darcspatch​ includes a test for this issue and a fix that makes the test pass.

comment:4 Changed at 2011-09-04T22:50:16Z by davidsarah

  • Keywords reviewed added; review-needed removed

Reviewed and manually smoke-tested, +1.

comment:5 Changed at 2011-09-05T02:05:40Z by davidsarah

  • Resolution set to fixed
  • Status changed from new to closed

Applied in 64996a913d014b5f.

Note: See TracTickets for help on using tickets.