Changes between Initial Version and Version 1 of Ticket #1732, comment 2


Ignore:
Timestamp:
2012-05-10T00:44:36Z (13 years ago)
Author:
davidsarah
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1732, comment 2

    initial v1  
    11I agree as well (in general I don't like overloading of the interpretation of one argument based on another argument, in any API).
    22
    3 Should {{{to_dircap}}} accept a path after the dircap? Note that supporting that would allow changing {{{tahoe mv}}} to use this API, which is a prerequisite to fixing #973 in the way proposed in ticket:973#comment:4 (since that fix depends on knowing the path that was used in the {{{tahoe mv}}} command to specify the destination). If it does accept a path then it should be called something other than {{{to_dircap}}}.
     3Should {{{to_dircap}}} accept a path after the dircap? Note that supporting that would allow changing {{{tahoe mv}}} to use this API, which is a prerequisite to fixing #943 in the way proposed in ticket:943#comment:4 (since that fix depends on knowing the path that was used in the {{{tahoe mv}}} command to specify the destination). If it does accept a path then it should be called something other than {{{to_dircap}}}.
    44
    55Unix {{{mv}}} can rename a file at the same time as moving it. Should there be a {{{to_name}}} argument (defaulting to {{{from_name}}})?
     6
     7[edit: fix wrong bug number for #943]