Re: [PATCH] Documentation/git-worktree: use working tree for trees on the file system

From: Michael J Gruber <git@grubix.eu>
Date: Apr 7, 2017, 13:59 UTC
Message-ID: <ee8e8671-066b-311e-8cad-31a1ab22eec7@grubix.eu>
In-Reply-To: <CACsJy8BNYmYarZqnERhsO8LDxdsMsviUMs3Co6C4Ed7W9OvDJQ@mail.gmail.com>

Duy Nguyen venit, vidit, dixit 25.03.2017 13:07:

Show 16 quoted lines

> On Fri, Mar 24, 2017 at 12:55 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> Michael J Gruber <git@drmicha.warpmail.net> writes:
>>
>>> Are we at a point where we can still rename the new feature at least? If
>>> yes, and keeping everything else is mandatory, than "workspace" or
>>> "working space" may be a serious contender for naming the new thing.
>>
>> I do not have a good answer to the first question, but workspace
>> does sound like a good name for what this feature is trying to
>> achieve.
>>
> 
> Now is not too late to rename the command from worktree to workspace
> (and keep "worktree" as an alias that will be eventually deleted).
> Should we do it? I would keep file names, function names... unchanged
> though, not worth the amount of new conflicts.

I guess I would go for a full change. Our technical documentation often merely consists of the source code, so we should reduce potential confusion there, too.

Michael