From: Junio C Hamano <gitster@pobox.com>
To: Thomas Bachem <mail@thomasbachem.com>
Cc: gitgitgadget@gmail.com, git@vger.kernel.org,
ben.knoble@gmail.com, phillip.wood@dunelm.org.uk, ps@pks.im
Subject: Re: [PATCH v3] t5520: don't expire reflogs where it matters
Date: Fri, 02 Oct 2026 08:04:17 -0700 [thread overview]
Message-ID: <xmqqfqyo16vi.fsf@gitster.g> (raw)
In-Reply-To: <CAA0xjtpM6t-Ga57UF0yrv7=ggz5GChHSk7hTQnGbVfAykhVmQw@mail.gmail.com> (Thomas Bachem's message of "Fri, 2 Oct 2026 11:23:49 +0200")
Thomas Bachem <mail@thomasbachem.com> writes:
> Hi Junio,
>
> On 02/10/2026 00:48, Junio C Hamano wrote in What's cooking [1]:
>> The t5520 test script has been updated to disable reflog expiration.
>> This prevents test flakiness caused by auto-maintenance running
>> geometric repack which would otherwise immediately expire the test's
>> reflogs due to them carrying hardcoded timestamps from 2005.
>
> It's the reflog-expire task of auto maintenance that expires the
> reflogs, not the geometric repack.
Indeed. Thanks.
prev parent reply other threads:[~2026-10-02 15:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 14:38 [PATCH] t5520: don't expire reflogs where it matters Thomas Bachem via GitGitGadget
2026-09-28 20:45 ` Ben Knoble
2026-09-29 11:48 ` D. Ben Knoble
2026-09-29 15:59 ` Junio C Hamano
2026-09-29 15:02 ` Junio C Hamano
2026-09-29 15:29 ` D. Ben Knoble
2026-09-30 0:44 ` Junio C Hamano
2026-09-29 17:08 ` [PATCH v2] " Thomas Bachem via GitGitGadget
2026-09-30 15:49 ` Phillip Wood
2026-10-01 8:07 ` Thomas Bachem
2026-10-01 8:24 ` [PATCH v3] " Thomas Bachem via GitGitGadget
2026-10-01 15:48 ` Phillip Wood
2026-10-02 9:23 ` Thomas Bachem
2026-10-02 15:04 ` Junio C Hamano [this message]
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=xmqqfqyo16vi.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=mail@thomasbachem.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
/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.