I most certainly didn't claim it was the point of GGP either. The point was that no evidence at all have been put forward that git-new-worktree is less "data safe" than the corresponding fossil solution, on the contrary…
This is a very vague statement, and contradicts your original claim. The way objects and branch references was set up by git-new-workdir was completely safe for git-gc not to lose other workdir's data. Other than that,…
> it took until 2015 to even support something as basic as multiple checkouts of the same repository via `git worktree` This feature was supported many years before that via a separate script.
I most certainly didn't claim it was the point of GGP either. The point was that no evidence at all have been put forward that git-new-worktree is less "data safe" than the corresponding fossil solution, on the contrary…
This is a very vague statement, and contradicts your original claim. The way objects and branch references was set up by git-new-workdir was completely safe for git-gc not to lose other workdir's data. Other than that,…
> it took until 2015 to even support something as basic as multiple checkouts of the same repository via `git worktree` This feature was supported many years before that via a separate script.