Re: Recovering from gc errors

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Nov 14, 2017, 16:48 UTC
Message-ID: <CAPig+cS8fg7UEX7eO4LLrVuuuBCxOVbhqmc5xFGqv3mT6s0=ng@mail.gmail.com>
In-Reply-To: <3af0f8cc-09f3-bcf2-04c8-f076e0ddcea2@xiplink.com>

On Tue, Nov 14, 2017 at 10:39 AM, Marc Branchaud <marcnarc@xiplink.com> wrote:

Show 7 quoted lines

> I'm willing to chalk this up to bugs in the early worktree code, unless one
> of the CC'd worktree developers thinks otherwise.
>
> An explicit "git worktree delete" command would be nice for manually
> cleaning things up.  It's easy to just delete the directory, but having a
> "delete" command gives the user assurance that they're not missing
> something.

Duy does have a series in 'pu' which adds this functionality, but I guess it's stalled for the moment. From "What's Cooking":

    * nd/worktree-move (2017-04-20) 6 commits
    - worktree remove: new command
    - worktree move: refuse to move worktrees with submodules
    - worktree move: accept destination as directory
    - worktree move: new command
    - worktree.c: add update_worktree_location()
    - worktree.c: add validate_worktree()

    "git worktree" learned move and remove subcommands.

    Expecting a reroll.
    cf. <20170420101024.7593-1-pclouds@gmail.com>
    cf. <20170421145916.mknekgqzhxffu7di@sigill.intra.peff.net>
    cf. <d0e81b1e-5869-299e-f462-4d43dc997bd1@ramsayjones.plus.com>