git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] t5520: don't expire reflogs where it matters

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 29, 2026, 15:02 UTC
Message-ID
<xmqqzex0hzhf.fsf@gitster.g>
In-Reply-To
<89E3CD2E-8366-4C5A-B3A4-8F44AC5F89DF@gmail.com>
Ben Knoble <ben.knoble@gmail.com> writes:
Show 7 quoted lines
>>    t5520: don't expire reflogs where it matters
>> 
>>    The t5520 failure Junio saw in 'seen' with Ben Knoble's stash series,
>>    bisected by Ben to tb/rerere-lock-grace and taken apart in the thread:
>>    https://lore.kernel.org/git/a59c4225-f093-4001-b77a-2083dfecce6e@gmail.com/
>
> Junio, if it’s simpler for you this way: I’ll just pick this patch into my series rather than wait for it to appear in seen and recreate my topic on master + it.

Either would work for me, but I created a synthetic base that includes this patch and queued your last iteration on top of it, before merging the result to 'seen' .

When you reroll, I'd reuse this synthetic base 4d7270214a (Merge branch 'tb/t5520-reflog-expire' into dk/stash-apply-index-incore, 2026-09-28)

Thanks.
Show 28 quoted lines
>> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-2243%2Fthomasbachem%2Ft5520-reflog-expire-v1
>> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2243/thomasbachem/t5520-reflog-expire-v1
>> Pull-Request: https://github.com/gitgitgadget/git/pull/2243
>> 
>> t/t5520-pull.sh | 6 ++++++
>> 1 file changed, 6 insertions(+)
>> 
>> diff --git a/t/t5520-pull.sh b/t/t5520-pull.sh
>> index 27f38ab3c8..bc818605a5 100755
>> --- a/t/t5520-pull.sh
>> +++ b/t/t5520-pull.sh
>> @@ -35,6 +35,12 @@ test_pull_autostash_fail () {
>> }
>> 
>> test_expect_success setup '
>> +    # Commit dates are hardcoded to 2005, and the reflog entries will have
>> +    # a matching timestamp. Maintenance may thus immediately expire
>> +    # reflogs if it was running.
>> +    git config set gc.reflogExpire never &&
>> +    git config set gc.reflogExpireUnreachable never &&
>> +
>>    echo file >file &&
>>    git add file &&
>>    git commit -a -m original
>> 
>> base-commit: 34f06850c16c7f7ac822b1adc71354f11b0f2ca3
>> --
>> gitgitgadget
Previous: Junio C HamanoNext: D. Ben Knoble
Message 5 of 14 in “t5520: don't expire reflogs where it matters”
  1. t5520: don't expire reflogs where it mattersThomas Bachem via GitGitGadget, Sep 28, 2026
  2. Ben KnobleSep 28, 2026
  3. D. Ben KnobleSep 29, 2026
  4. Junio C HamanoSep 29, 2026
  5. Junio C HamanoSep 29, 2026
  6. D. Ben KnobleSep 29, 2026
  7. Junio C HamanoSep 30, 2026
  8. t5520: don't expire reflogs where it mattersThomas Bachem via GitGitGadget, Sep 29, 2026
  9. Phillip WoodSep 30, 2026
  10. Thomas BachemOct 1, 2026
  11. t5520: don't expire reflogs where it mattersThomas Bachem via GitGitGadget, Oct 1, 2026
  12. Phillip WoodOct 1, 2026
  13. Thomas BachemOct 2, 2026
  14. Junio C HamanoOct 2, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.