From: Stefan Sperling <stsp@stsp.name>
Subject: Re: add remove but keep files
To: Tracey Emery <tracey@traceyemery.net>
Cc: gameoftrees@openbsd.org
Date: Fri, 13 Dec 2019 19:41:58 +0100

On Fri, Dec 13, 2019 at 11:29:45AM -0700, Tracey Emery wrote:
> @@ -655,6 +655,22 @@ are as follows:
>  .Bl -tag -width Ds
>  .It Fl f
>  Perform the operation even if a file contains uncommitted modifications.
> +.It Fl k
> +Keep affected files on disk.
> +Before the next commit,
> +.Cm got status
> +will list the files with status:
> +.Bl -column YXZ description
> +.It D Ta file scheduled for deletion in next commit
> +.El
> +.Pp
> +After the next commit,
> +.Cm got status
> +will list the files with status:
> +.Bl -column YXZ description
> +.It ? Ta unversioned item not tracked by
> +.Nm
> +.El
>  .It Fl R
>  Permit recursion into directories.
>  If this option is not specified,

Hmm, that seems kind of long-winded. Could we use a single sentence like:
 'got status' will report affected file as deleted until the next commit,
 and as unversioned after the next commit.

Or perhaps documenting this is not such a good idea after all?
status 'D' and '?' are kind of obvious expected results.

Your call :)

Looks great otherwise!