Re: [Monotone-devel] [PATCH] Make --execute default

[Zack Weinberg]

On 2/26/07, William Uther <address@hidden> wrote:
> > mtn drop ${STH}:
> >  - file ${STH} exists
>
> File exists and is under version control and is unchanged:
>    deleted with message about dropping from manifest (as currently -
> maybe should change?)
>
> File exists and is under version control and is changed:
>    dropped but not deleted - warning given
>
> File exists and is not under version control:
>    not deleted - warning given
>
> File doesn't exist and but is under version control:
>    dropped from manifest with message
>
> File doesn't exist and is not under version control:
>    Warning given

What about a file that exists and has just been "add"ed, so it is
technically under version control but no version exists in the
database yet?  [Suggest warning, dropping it from the manifest but not
deleting the file.  This is the natural (IMO) way to recover from
accidentally adding a file that shouldn't have been added.]

> >  - dir ${STH} exists and is empty
>
> exists and is empty and under version control.
>    deleted with message about dropping from manifest (as currently -
> maybe should change?)
>
> exists and is empty and NOT under version control
>    not deleted - warning given

Same question as above.

> dir exists, but has untracked children and -R is given
>    dir dropped but not deleted and warning given

I am tempted to request a special case for when every single untracked
child is an ignored file: move the directory into _MTN/trash/ and
print a warning.  (I'm not convinced this is a good idea.  Talk to
Derek, he was working on recovering from this sort of situation.)

zw