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

Re: checkout: clarify "up to date with origin/" uses local remote-tracking ref

From
Ben Knoble <ben.knoble@gmail.com>
Date
Apr 7, 2026, 16:13 UTC
Message-ID
<5DFBE9D6-0EC8-4702-99C5-827AEF8C6265@gmail.com>
In-Reply-To
<xmqq4ilm7q1n.fsf@gitster.g>
Show 21 quoted lines
> 
> Le 7 avr. 2026 à 11:28, Junio C Hamano <gitster@pobox.com> a écrit :
> 
> Jesko Schwarzer <jesko@schwarzers.de> writes:
> 
>> Would the project consider one of the following?
>>     1. *Clearer messaging*, e.g. indicating that the comparison is
>> against the last-known origin/<branch> (or similar wording that does not
>> imply a live remote check).
> 
> Surely.  Patches to start discussions are very much welcome.
> 
>>     2. *Optional context* when available (e.g. from reflog or last
>> fetch time), so users know how stale the origin/* ref might be — if that
>> is technically and policy-wise acceptable.
> 
> I am imagining that #1 above would add something that conveys
> "relative to the last known state", and this will extend/replace the
> phrase you would choose for "the last known state" with "as of N
> days ago" or something when necessary pieces of information is
> available, right?  That sounds entirely feasible.
I seem to recall a recent (last ~6 months) thread about “last fetch time” and there being some question of how to record it. Alas I haven’t searched the archives to find it. 
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “checkout: clarify "up to date with origin/" uses local remote-tracking ref”
  1. Jesko SchwarzerApr 7, 2026
  2. Junio C HamanoApr 7, 2026
  3. Ben KnobleApr 7, 2026
  4. Junio C HamanoApr 7, 2026
  5. Junio C HamanoApr 7, 2026
  6. D. Ben KnobleApr 8, 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.