Changes between Initial Version and Version 2 of Ticket #1506


Ignore:
Timestamp:
2011-08-26T20:25:20Z (13 years ago)
Author:
davidsarah
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1506

    • Property Keywords mutable mdmf tahoe-put usability added
    • Property Component changed from unknown to code-frontend-cli

  • Ticket #1506 – Description

    initial v2  
    1 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.
     1Currently, 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.
    22
    3 (this improvement was suggested by davidsarah in [http://tahoe-lafs.org/trac/tahoe-lafs/ticket/393#comment:141 #393, comment 141])
     3(This improvement was suggested by davidsarah in [http://tahoe-lafs.org/trac/tahoe-lafs/ticket/393#comment:141 #393, comment 141].)