Changes between Version 3 and Version 4 of Ticket #2027


Ignore:
Timestamp:
2013-07-17T16:22:30Z (11 years ago)
Author:
daira
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2027

    • Property Summary changed from Inconsistent 'tahoe cp' Behavior to Inconsistent 'tahoe cp' behavior

  • Ticket #2027 – Description

    v3 v4  
    11When copying a file from the top level of a directory node using the CLI, tahoe requires a file name to be specified.
    22
    3 Ex: {{{tahoe cp tahoe:test.jpg ~}}} fails with the following assertion traceback, while {{{tahoe cp tahoe:test.jpg ~/test.jpg }}} succeeds.
     3Ex: {{{tahoe cp tahoe:Seattle.jpg ~}}} fails with the following assertion traceback, while {{{tahoe cp tahoe:Seattle.jpg ~/Seattle.jpg}}} succeeds.
    44
    55{{{
    … …  
    3333However, when a file is copied from a subdirectory to the local disk without a specified file name, the download will succeed.
    3434
    35 Ex: {{{tahoe cp tahoe:test/test.jpg ~}}} succeeds along with {{{tahoe cp tahoe:test/test.jpg ~/test.jpg}}}.
     35Ex: {{{tahoe cp tahoe:test/Seattle.jpg ~}}} succeeds along with {{{tahoe cp tahoe:test/Seattle.jpg ~/Seattle.jpg}}}.
    3636
    37 The CLI's behavior should be consistent. Either require users to specify a file name for all cp actions or allow users to copy files from the top level of a directory  to a local directory without specifying a file name.
     37All four cases should succeed.