2010/9/16 Eric Uhrhane er...@google.com:
How about this?
For a move/copy of a file on top of existing file, or a directory on
top of an existing empty directory, you get an automatic overwrite.
A move/copy of a file on top of an existing directory, or of a
directory on top of an existing
How about this?
For a move/copy of a file on top of existing file, or a directory on
top of an existing empty directory, you get an automatic overwrite.
A move/copy of a file on top of an existing directory, or of a
directory on top of an existing file, will always fail.
A move/copy of a file or
2010/9/16 Kinuko Yasuda kin...@chromium.org:
On Thu, Sep 16, 2010 at 2:50 PM, Eric Uhrhane er...@google.com wrote:
How about this?
For a move/copy of a file on top of existing file, or a directory on
top of an existing empty directory, you get an automatic overwrite.
A move/copy of a file on
On Thu, Sep 16, 2010 at 4:00 PM, Eric Uhrhane er...@google.com wrote:
2010/9/16 Kinuko Yasuda kin...@chromium.org:
On Thu, Sep 16, 2010 at 2:50 PM, Eric Uhrhane er...@google.com wrote:
How about this?
For a move/copy of a file on top of existing file, or a directory on
top of an existing
On Thu, Sep 9, 2010 at 12:12 AM, Kinuko Yasuda kin...@chromium.org wrote:
On Tue, Sep 7, 2010 at 6:12 PM, Eric Uhrhane er...@google.com wrote:
On Mon, Aug 30, 2010 at 9:27 PM, Kinuko Yasuda kin...@chromium.org
wrote:
Hi,
I have a question about Entry.moveTo/copyTo behavior defined in
I think recursive copy/remove is a very valid use case. As for overwrite, is
a flag necessary? On most OSes you already get overwrite as the default
behaviour (at least from APIs, many interactive UAs such as Explorer on
windows will prompt), is there a compelling argument why it should be
On Mon, Aug 30, 2010 at 9:27 PM, Kinuko Yasuda kin...@chromium.org wrote:
Hi,
I have a question about Entry.moveTo/copyTo behavior defined in
the File API: Directories and System [1].
Currently the API doesn't specify how Entry.moveTo() and copyTo() should
behave
when a source entry is a
Hi,
I have a question about Entry.moveTo/copyTo behavior defined in
the File API: Directories and System [1].
Currently the API doesn't specify how Entry.moveTo() and copyTo() should
behave
when a source entry is a file and there's *already* a file at the
destination path.
Should UAs overwrite
