Thread (1 message) 1 message, 1 author, 2025-02-04

Fwd: Usability issue: "Your branch is up to date"

From: Bram van Oosterhout <hidden>
Date: 2025-02-04 00:51:17

---------- Forwarded message ---------
From: Bram van Oosterhout <redacted>
Date: Tue, Feb 4, 2025 at 11:47 AM
Subject: Re: Usability issue: "Your branch is up to date"
To: Chris Torek <redacted>


On Tue, Feb 4, 2025 at 11:32 AM Chris Torek [off-list ref] wrote:
On Mon, Feb 3, 2025 at 4:28 PM Bram van Oosterhout
[off-list ref] wrote:
quoted
Ahhhh, this thread explains my confusion when, even though git locally
tells me my branch is "up to date", a fetch demonstrates the branch is
not up to date.

Which begs the question: Why does git say: "Your branch is up to date
..." if at best it can say: "Your
branch MIGHT BE up to date with ..."?
(resend: I perpetuated the reply/reply all mistake)
Perhaps a small wording change is in order, to say "your branch is
up to date as of the most recent information I have from git fetch".
Or perhaps: "Your local branch is unchanged since your last fetch from ...".
That says that I have not made any changes since I last fetched the
branch and suggests there could be changes in the remote branch.

Bram
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help