From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 25 Sep 2026 21:58:46 GMT
Subject: Re: [PATCH v2] push: fix --force-if-includes when remote-tracking ref has no reflog
Message-ID: <xmqqfqyxt2ll.fsf@gitster.g>
In-Reply-To: <arbfQ7xF1NgDeilU@localhost.localdomain>

Tyler Cipriani <tyler@tylercipriani.com> writes:

> So date=0 is always correct and should have equivalent in runtime in
> most cases. And it neatly side-steps what cut off should we use?
> gc.reflogExpire vs.  gc.<remote>.reflogExpire vs.
> gc.<local>.reflogExpire vs. flat 90 days vs. do we respect
> gc.reflogExpire=never.

With a reflog that has never been expired, using all the available
information will always work with better information than with
cutoff, so that is not surprising at all ;-).