Nguyễn Thái Ngọc Duy <[email protected]> writes: > @@ -11,6 +11,7 @@ SYNOPSIS > [verse] > 'git worktree add' [-f] [--detach] [--checkout] [-b <new-branch>] <path> > [<branch>] > 'git worktree list' [--porcelain] > +'git worktree lock' [--reason <string>] <worktree> > 'git worktree prune' [-n] [-v] [--expire <expire>]
This seems to be based on an unseen version that lists 'list' before 'prune' here and other places. I'd appreciate it if you either make sure a series that introduces a new feature applies cleanly to my tree before sending it out, or clarify to what state the series is designed to apply, when you send a patch series next time. > @@ -110,6 +118,15 @@ OPTIONS > --expire <time>:: > With `prune`, only expire unused working trees older than <time>. > > +--reason <string>: Double-colon, I think (locally fixable). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
