Re: [PATCH v2] push: fix --force-if-includes when remote-tracking ref has no reflog

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 25, 2026, 21:58 UTC
Message-ID: <xmqqfqyxt2ll.fsf@gitster.g>
In-Reply-To: <arbfQ7xF1NgDeilU@localhost.localdomain>

Tyler Cipriani <tyler@tylercipriani.com> writes:

Show 5 quoted lines

> 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 ;-).

$ 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.