[tahoe-lafs-trac-stream] [tahoe-lafs] #1506: mutable-type should imply mutable in tahoe put

[tahoe-lafs]

#1506: mutable-type should imply mutable in tahoe put
---------------------+-------------------------
 Reporter:  kevan    |          Owner:  kevan
     Type:  defect   |         Status:  new
 Priority:  major    |      Milestone:  1.9.0
Component:  unknown  |        Version:  1.9.0a1
 Keywords:           |  Launchpad Bug:
---------------------+-------------------------
 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 [http://tahoe-
 lafs.org/trac/tahoe-lafs/ticket/393#comment:141 #393, comment 141])

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1506>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage