Stefan Beller <[email protected]> writes: > (e.g. work tree for working tree?)
This was probably primarily my fault, not just because I've written more than my share of documentation (compared to the code that touched), but I was deliberately writing "work tree" when both "work tree" and "working tree" terms meant the same thing. Compared to the length of the timeperiod, the newcomer who is now known as "worktree" has only lived a very short period of time, so it is not surprising to see remaining "work tree" in our documentation set. I think some attempts like 06cdac5a (git-reset.txt: use "working tree" consistently, 2010-09-15) were made to clean things up even before "worktree" started to mean an entirely different thing, and we shouldn't make things worse by adding mentions of "work tree" when we mean "working tree". -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
