On Fri, Jan 17, 2020 at 7:25 AM Philippe Blain via GitGitGadget
<gitgitgadget@xxxxxxxxx> wrote:
> When 'checkout --to' functionality was moved to 'worktree add', tests were adapted
> in f194b1ef6e (tests: worktree: retrofit "checkout --to" tests for "worktree add",
> 2015-07-06).
>
> The calls were changed to 'worktree add' in this test (then t7410), but the test
> descriptions were not updated, keeping 'checkout' instead of using the new
> terminology (linked worktrees).
>
> Clarify the tests by using the right terminology. While at it, remove some unnecessary
> leading directories such that all superproject worktrees are directly next to one
> another in the trash directory.
The unanswered questions which popped into my head when reading the
"While at it..." include:
Why is it desirable for the worktrees to live in this new location
rather than their original locations?
Is it safe to relocate the worktrees like this without losing some
important aspect of the test?
Why were the worktrees located as they were originally? Was there
some hidden or not-so-obvious reason that we're overlooking? (I
guess this is really the same as question #2.)
