On Wed, Jul 14, 2021 at 10:32 PM Stephen Manz via GitGitGadget <gitgitgadget@xxxxxxxxx> wrote: > The default reason stored in the lock file, "added with --lock", is unlikely > to be what the user would have given in a separate git worktree lock > command. Allowing --reason to be specified along with --lock when adding a > working tree gives the user control over the reason for locking without > needing a second command. > > Changes since v3: > > * Updated test to define a shell variable, lock_reason, set to "why not". > Expand the variable to use with --reason and to echo to file, expected. > This avoids the spacing comment made by Eric Sunshine. Thanks, these changes look fine to me. I don't know whether or not Junio has merged this series down to his "next" branch yet locally, though. If he has, then he may not pick up your v4, and this minor cleanup change could instead be done as a standalone patch atop v3 (or could be dropped since v3 was probably "good enough"). In any case, this series is still Reviewed-by: me.
