Re: What's cooking in git.git (Sep 2018, #01; Tue, 4)
- Date: Wed, 5 Sep 2018 16:31:11 -0400
- From: Jeff King <peff@xxxxxxxx>
- Subject: Re: What's cooking in git.git (Sep 2018, #01; Tue, 4)
On Wed, Sep 05, 2018 at 05:50:04AM -0400, Eric Sunshine wrote:
> On Tue, Sep 4, 2018 at 6:36 PM Junio C Hamano <gitster@xxxxxxxxx> wrote:
> > * 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 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
> : https://public-inbox.org/git/20180830075431.GF11944@xxxxxxxxxxxxxxxxxxxxx/
Yeah, I'm not sure which is easier for Junio. I figured by replying
inline, it makes it easy to pick up on top of the others (since it
really does depend on them and should be in the same topic). But it is
easier to overlook as "meh, just more discussion".
Either way, yes, I'd be happy to see that patch on top.