Eric Sunshine <sunshine@xxxxxxxxxxxxxx> writes: > This patch series removes specialized knowledge from the libified > worktree code about how front-end "git worktree list" wants worktrees > sorted, and instead makes it the responsibility of "git worktree list" > itself to do the sorting. > > It is built atop es/worktree-duplicate-paths since that series adds > another caller of get_worktrees() which this series touches. > > A possible argument against this patch series is that some other entity > may someday want worktrees sorted in the same fashion as "git worktree > list", however, that seems a case of YAGNI. Is anything hurting to have the "mostly extra" flag and its handling that is added only to support "worktree list"? That would be another possible argument against this clean-up. Having said that, I think this is good. Thanks. Will queue.
