From: Junio C Hamano <gitster@pobox.com>
To: Tao Klerks <tao@klerks.biz>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2022, #07; Fri, 25)
Date: Tue, 01 Mar 2022 10:06:42 -0800 [thread overview]
Message-ID: <xmqqfso1r1hp.fsf@gitster.g> (raw)
In-Reply-To: <CAPMMpohJsZahwzhstoqxPZz=UbJ_7+vrUQZbk0DOrGFJ4Xq-nw@mail.gmail.com> (Tao Klerks's message of "Tue, 1 Mar 2022 12:56:52 +0100")
Tao Klerks <tao@klerks.biz> writes:
> On Mon, Feb 28, 2022 at 2:47 PM Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>>
>>
>>
>> Perhaps something like this:
>>
>> The performance of the "untracked cache" feature has been improved in
>> common cases where "--untracked-files=<mode>" and
>> "status.showUntrackedFiles" were combined. This change benefits Windows
>> users using it in conjuction with the "fsmonitor feature in particular.
>>
>> Perhaps adding:
>>
>> There's an obscure case where the performance is now worse, but it's
>> thought not to matter.
>>
>
> I really like it, thx! I would change "combined" to "aligned", and little else:
>
> The performance of the "untracked cache" feature has been improved in
> common cases where "--untracked-files=<mode>" and
> "status.showUntrackedFiles" were aligned. This change benefits Windows
> users using it in conjunction with the "fsmonitor" feature in particular.
> There's an obscure case where the performance is now worse, but it's
> thought not to matter.
Overly long for a topic summary, with value judgements that I'd
prefer to omit. What (you think) is "common" does not help us make
a stronger case. I've never said I agree "it's thought not to
matter" at all. Just stick to the known facts.
next prev parent reply other threads:[~2022-03-01 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 2:44 What's cooking in git.git (Feb 2022, #07; Fri, 25) Junio C Hamano
2022-02-26 8:54 ` en/merge-tree (Was: Re: What's cooking in git.git (Feb 2022, #07; Fri, 25)) Elijah Newren
2022-02-26 9:11 ` en/present-despite-skipped " Elijah Newren
2022-03-07 16:15 ` Johannes Schindelin
2022-02-28 12:38 ` What's cooking in git.git (Feb 2022, #07; Fri, 25) Tao Klerks
2022-02-28 13:42 ` Ævar Arnfjörð Bjarmason
2022-03-01 11:56 ` Tao Klerks
2022-03-01 18:06 ` Junio C Hamano [this message]
2022-03-01 19:25 ` Tao Klerks
2022-02-28 13:56 ` ds/commit-graph-gen-v2-fixes (was Re: What's cooking in git.git (Feb 2022, #07; Fri, 25)) Derrick Stolee
2022-02-28 14:10 ` ab/test-lib-tweaks (was: " Ævar Arnfjörð Bjarmason
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=xmqqfso1r1hp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=tao@klerks.biz \
/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.