From: Junio C Hamano <gitster@pobox.com>
To: Ben Knoble <ben.knoble@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>,
Thomas Bachem via GitGitGadget <gitgitgadget@gmail.com>,
Patrick Steinhardt <ps@pks.im>,
Thomas Bachem <mail@thomasbachem.com>
Subject: Re: [PATCH] t5520: don't expire reflogs where it matters
Date: Tue, 29 Sep 2026 17:44:22 -0700 [thread overview]
Message-ID: <xmqq4if7effd.fsf@gitster.g> (raw)
In-Reply-To: <xmqqzex0hzhf.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 29 Sep 2026 08:02:52 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> 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)
As Thomas updated the patch, I also had to update the synthetic
base. It is now 59d1ce1b6e (Merge branch 'tb/t5520-reflog-expire'
into dk/stash-apply-index-incore, 2026-09-29).
next prev parent reply other threads:[~2026-09-30 0:44 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 [this message]
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
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=xmqq4if7effd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox