DECISION: what reconstruct -f should do

David Lang david.lang at
Tue Apr 26 13:22:21 EDT 2011

On Tue, 26 Apr 2011, Bron Gondwana wrote:

> On Tue, 26 Apr 2011 10:19 -0700, "David Lang" <david.lang at> 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.
>> if you don't create INBOX.sub and the user wants it, will they run into any
>> grief when they try to create INBOX.sub due to the fact that the directory
>> already exists?
> No, that's not a problem.  It will create just fine.

Ok, in this case your logic makes sense.

I would suggest that reconstruct report these cases, so that if the user did 
want INBOX.sub they have a reminder from the fact that it could have been 
created, but was not.

David Lang

More information about the Info-cyrus mailing list