> For what it's worth, this conversation makes me think it was a mistake > to call this construct a worktree.
So the way forward is to purge the use of "worktree" meaning actual working trees? Thanks, Stefan Stefan Beller (2): git.c: introduce --working-tree superseding --work-tree revparse: introduce --is-inside-working-tree Documentation/git-rev-parse.txt | 4 ++-- Documentation/git.txt | 12 ++++++------ builtin/rev-parse.c | 3 ++- git.c | 5 +++-- 4 files changed, 13 insertions(+), 11 deletions(-) -- 2.12.0.306.g4a9b9b32d4.dirty
