Re: What's cooking in git.git (Sep 2018, #01; Tue, 4)
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Sep 5, 2018, 09:50 UTC
- Message-ID
- <CAPig+cSETNc5nRxf_zQq6JE8zNyUvKmdPWNsm6=NMSOXm2DV=A@mail.gmail.com>
- In-Reply-To
- <xmqqmusw6gbo.fsf@gitster-ct.c.googlers.com>
On Tue, Sep 4, 2018 at 6:36 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
> * es/worktree-forced-ops-fix (2018-08-30) 9 commits > - worktree: delete .git/worktrees if empty after 'remove' > - worktree: teach 'remove' to override lock when --force given twice > - worktree: teach 'move' to override lock when --force given twice > - worktree: teach 'add' to respect --force for registered but missing path > - worktree: disallow adding same path multiple times > - worktree: prepare for more checks of whether path can become worktree > - worktree: generalize delete_git_dir() to reduce code duplication > - worktree: move delete_git_dir() earlier in file for upcoming new callers > - worktree: don't die() in library function find_worktree() > > Various subcommands of "git worktree" take '--force' but did not > behave sensibly, which has been corrected.
This series is missing a patch[1] from Peff which he wanted placed at the end of the series. It was probably overlooked since he embedded it as a reply in that thread rather than sending it as a standalone patch.
[1]: https://public-inbox.org/git/20180830075431.GF11944@sigill.intra.peff.net/