Re: [PATCH v2] reflog: fix default expiry periods
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 24, 2026, 17:45 UTC
- Message-ID
- <xmqqecei35n2.fsf@gitster.g>
- In-Reply-To
- <20260924154659.GA736248@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 15 quoted lines
> On Thu, Sep 24, 2026 at 04:12:04PM +0200, Patrick Steinhardt wrote:
>
>> > > #define REFLOG_EXPIRE_OPTIONS_INIT(now) { \
>> > > - .default_expire_total = now - 30 * 24 * 3600, \
>> > > - .default_expire_unreachable = now - 90 * 24 * 3600, \
>> > > + .default_expire_total = now - 90 * 24 * 3600, \
>> > > + .default_expire_unreachable = now - 30 * 24 * 3600, \
>> > > }
>> >
>> > and the fix is very straight-forward.
>>
>> Is this something that we want to fast-track for Git 2.56?
>
> The breakage was in v2.50.0, so it is not a new regression. OTOH it
> seems quite obvious and low-risk. I'd be OK either way.Yeah, I didn't know the breakage was that old. Perhaps not many people are paying attention to reflog expiration?