On Fri, Aug 25, 2017 at 10:18 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Stefan Beller <sbeller@xxxxxxxxxx> writes: > >> Currently the worktree command gives its usage, when no subcommand is >> given. However there are no general options, all options are related to >> the subcommands itself, such that: >> >> $ git worktree >> usage: git worktree add [<options>] <path> [<branch>] >> or: git worktree list [<options>] >> or: git worktree lock [<options>] <path> >> or: git worktree prune [<options>] >> or: git worktree unlock <path> >> >> >> $ >> >> Note the two empty lines at the end of the usage string. This is because >> the toplevel usage is printed with an empty options list. >> >> Only print one new line after the usage string if the option list is empty. > > Good find. Shouldn't the last word in the sentence "non-empty", though?\ Yes. Originally I wrote a lot more and then deleted it all, mixing up the negations of what I was trying to say.
