From: Junio C Hamano <gitster@pobox.com>
To: Jeff Hostetler <git@jeffhostetler.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2022, #05; Wed, 14)
Date: Fri, 16 Dec 2022 07:37:35 +0900 [thread overview]
Message-ID: <xmqqfsdgqonk.fsf@gitster.g> (raw)
In-Reply-To: <aedc0911-5538-603e-b0e0-71435039545e@jeffhostetler.com> (Jeff Hostetler's message of "Wed, 14 Dec 2022 14:18:01 -0500")
Jeff Hostetler <git@jeffhostetler.com> writes:
> On 12/14/22 4:59 AM, Junio C Hamano wrote:
>> * jh/t7527-unflake-by-forcing-cookie (2022-12-02) 1 commit
>> - fsmonitor: fix race seen in t7527
>> Make fsmonitor more robust to avoid the flakiness seen in t7527.
>> Will merge back to 'next'.
>> source:<pull.1437.git.1669937534944.gitgitgadget@gmail.com>
>>
>
> There was no discussion on this item and nothing needs to be
> revisited, so it could go as is.
No discussion is not a good news, though.
Always using cookie files means we no longer sometimes use them and
sometimes not---which means fewer variations to think about and in
general is a good thing.
As you explain in the last paragraph of the proposed log message, if
the test caught a bug introduced by a premature optimization that
was not-well-thought-out, the test served its purpose very well.
Good.
Let's mark it as "Will merge to 'next'" again.
Thanks.
next prev parent reply other threads:[~2022-12-15 22:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 9:59 What's cooking in git.git (Dec 2022, #05; Wed, 14) Junio C Hamano
2022-12-14 10:44 ` Junio C Hamano
2022-12-14 19:46 ` Taylor Blau
2022-12-14 15:09 ` Derrick Stolee
2022-12-14 23:50 ` Junio C Hamano
2022-12-14 19:09 ` Jeff Hostetler
2022-12-14 23:50 ` Junio C Hamano
2022-12-14 19:18 ` Jeff Hostetler
2022-12-15 22:37 ` Junio C Hamano [this message]
2022-12-15 9:14 ` ag/merge-strategies-in-c (was: What's cooking in git.git (Dec 2022, #05; Wed, 14)) Ævar Arnfjörð Bjarmason
2022-12-15 12:55 ` Phillip Wood
2022-12-15 15:32 ` Ævar Arnfjörð Bjarmason
2022-12-15 16:27 ` Phillip Wood
2022-12-15 16:29 ` Ævar Arnfjörð Bjarmason
2022-12-15 9:33 ` ab/remove--super-prefix & ab/submodule-no-abspath " Ævar Arnfjörð Bjarmason
2022-12-15 9:49 ` js/bisect-in-c " Ævar Arnfjörð Bjarmason
2022-12-15 11:55 ` What's cooking in git.git (Dec 2022, #05; Wed, 14) Sean Allred
2022-12-15 22:45 ` Junio C Hamano
2022-12-15 23:09 ` Junio C Hamano
2022-12-16 15:33 ` ds/bundle-uri-4* (was Re: What's cooking in git.git (Dec 2022, #05; Wed, 14)) Derrick Stolee
2022-12-16 22:55 ` 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=xmqqfsdgqonk.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
/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.