DECISION: what reconstruct -f should do

Bron Gondwana brong at fastmail.fm
Wed Apr 27 00:59:50 EDT 2011


On Wed, Apr 27, 2011 at 10:31:40AM +0900, OBATA Akio wrote:
> On Wed, 27 Apr 2011 02:20:51 +0900, Bron Gondwana <brong at fastmail.fm> wrote:
> 
> >On Tue, 26 Apr 2011 10:19 -0700, "David Lang" <david.lang at digitalinsight.com> wrote:
> >>I can easily see someone wanting to have INBOX.sub containing INBOX.sub.folder1
> >>and INBOX.sub.folder2 as an organizational mechanism
> >>
> >>if you were to create INBOX.sub and the user didn't want it, could they remove
> >>it without affecting INBOX.sub.folder?
> >
> >No, not easily.  It would delete the whole tree by default.
> 
> No, "RENAME" will affect to whole tree, but "DELETE" is not.

Yes, you're right.  Of course, delete is a rename now - but not
up at the level where that happens.

A lot of clients do convert a delete into a tree delete though
(or a rename under Trash in some cases)

Bron.


More information about the Info-cyrus mailing list