From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "Derrick Stolee" <stolee@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Elijah Newren" <newren@gmail.com>,
"Jean-Noël AVILA" <jn.avila@free.fr>
Subject: Re: ds/sparse-checkout-requires-per-worktree-config (was Re: What's cooking in git.git (Feb 2022, #02; Wed, 9))
Date: Tue, 15 Feb 2022 17:55:21 -0800 [thread overview]
Message-ID: <xmqqzgmrwp6e.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cR+n=LQg5AJQgGQXuYStN90-jExWnE45sS1EXo+O8dQgQ@mail.gmail.com> (Eric Sunshine's message of "Tue, 15 Feb 2022 17:40:35 -0500")
Eric Sunshine <sunshine@sunshineco.com> writes:
> I wouldn't go so far as to characterize it as a disagreement. In my
> review, I only pointed out that this series was introducing some new
> instances of inconsistency which some earlier efforts (started by
> Michael Haggerty) had eliminated. As mentioned in [2], I personally
> prefer the term "worktree".
These two words mean different things, so I am not sure there is
much room for personal preference. If what a documentation refers
to is the working tree plus its administrative files, referring to
the whole as a "worktree" would be more precise and concise. If the
discussion is only about the thing above .git/ that the editors and
the compilers see, "working tree" is the right term to use.
next prev parent reply other threads:[~2022-02-16 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 0:12 What's cooking in git.git (Feb 2022, #02; Wed, 9) Junio C Hamano
2022-02-11 13:40 ` ds/sparse-checkout-requires-per-worktree-config (was Re: What's cooking in git.git (Feb 2022, #02; Wed, 9)) Derrick Stolee
2022-02-11 16:51 ` Junio C Hamano
2022-02-15 22:40 ` Eric Sunshine
2022-02-16 1:55 ` Junio C Hamano [this message]
2022-02-11 21:01 ` What's cooking in git.git (Feb 2022, #02; Wed, 9) Jean-Noël AVILA
2022-02-11 22:38 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzgmrwp6e.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=newren@gmail.com \
--cc=stolee@gmail.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.