Re: [PATCH] tests: rename work-tree tests to *work-tree*

Michael J Gruber writes: >> That is rather unfortunate. Most of them predate the "worktree" >> subcommand, I think, and having to rename them merely because a >> subcommand with a confusing name appeared sound somewhat backwards. > > The question is: What ist the way

Re: [PATCH] tests: rename work-tree tests to *work-tree*

Junio C Hamano venit, vidit, dixit 20.02.2016 22:42: > Michael J Gruber writes: > >> "Work tree" or "working tree" is the name of a checked out tree, >> "worktree" the name of the command which manages several working trees. >> The naming of tests mixes these two,

Re: [PATCH] tests: rename work-tree tests to *work-tree*

Michael J Gruber writes: > "Work tree" or "working tree" is the name of a checked out tree, > "worktree" the name of the command which manages several working trees. > The naming of tests mixes these two, currently: > > $ls t/*worktree* > ... > Rename t1501, t1509 and

[PATCH] tests: rename work-tree tests to *work-tree*

"Work tree" or "working tree" is the name of a checked out tree, "worktree" the name of the command which manages several working trees. The naming of tests mixes these two, currently: $ls t/*worktree* t/t1501-worktree.sh t/t1509-root-worktree.sh t/t2025-worktree-add.sh t/t2026-worktree-prune.sh