Re: What's cooking in git.git (Sep 2020, #01; Tue, 1)

[Junio C Hamano <gitster@pobox.com>]

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Tue, Sep 1, 2020 at 5:30 PM Junio C Hamano <gitster@pobox.com> wrote:
>> * jc/run-command-use-embedded-args (2020-08-26) 1 commit
>>  Various callers of run_command API has been modernized.
>
> s/has/have/
>
>> * es/worktree-repair (2020-08-31) 5 commits
>>   (merged to 'next' on 2020-08-31 at 604825c5e4)
>>  + init: make --separate-git-dir work from within linked worktree
>>  + init: teach --separate-git-dir to repair linked worktrees
>>  + worktree: teach "repair" to fix outgoing links to worktrees
>>  + worktree: teach "repair" to fix worktree back-links to main worktree
>>  + worktree: add skeleton "repair" command
>>
>>  "git worktree repair" command to correct on-disk pointers between
>>  the repository and its secondary working trees.
>
> I wonder if this could be reworded so it's clearer that "git worktree
> repair" is a new command, and to mention fixes to "git init
> --separate-git-dir". Perhaps like this?
>
>     "git worktree" gained a "repair" subcommand to help users recover
>     from problems arising from factors outside of Git's control.
>     Also, "git init --separate-git-dir" no longer corrupts
>     administrative data related to linked worktrees.

OK that reads much better.

-from problems arising from factors outside of Git's control.
+after moving the worktrees manually without telling Git.

The latter is slightly shorter; does the "repair" help situations
other than that, or is the above cover all the "factors outside" out
control?

Thanks.