Eric Sunshine <sunshine@xxxxxxxxxxxxxx> writes:
> "reasons". That possibility suggests that this particular
> reason-giving option of `git worktree add` ought to be named
> `--lock-reason`, but `git worktree add --lock --lock-reason=<reason>`
> feels clunky and redundant, which is why I was wondering if `git
> worktree --lock[=<reason>]` would be a better (and more convenient)
> UI.
Sure, but
$ git worktree add --lock --reason=why-do-i-want-to-lock \
--frotz --reason=why-do-i-want-to-frotz
would work just fine, no?
