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

Request re git status

From
RPRon Pero <rpero@magnadev.com>
Date
Feb 6, 2017, 23:35 UTC
Message-ID
<CANOj2JG5VuDtS30PfOrZ=4q8pTv_frY7=p+0g=UW3yV6ev+1KQ@mail.gmail.com>
Hi

I almost got bit by git: I knew there were changes on the remote server, but git status said I was uptodate with the remote.

This page explains it well.
http://stackoverflow.com/questions/27828404/why-does-git-status-show-branch-is-up-to-date-when-changes-exist-upstream
That page also contains a good suggestion:

Why ... not design it to [optionally] DO a fetch and THEN declare whether it is up to date? Or change the message to tell what it really did, e.g. "Your branch was up-to-date with 'origin/master' when last checked at {timestamp}"? Or even just say, "Do a fetch to find out whether your branch is up to date"?

Thanks, and best wishes,
Ron
Next: Phil Hord
Message 1 of 10 in “Request re git status”
  1. Ron PeroFeb 6, 2017
  2. Phil HordFeb 7, 2017
  3. Ron PeroFeb 7, 2017
  4. Konstantin KhomoutovFeb 7, 2017
  5. Samuel LijinFeb 7, 2017
  6. Jacob KellerFeb 7, 2017
  7. Duy NguyenFeb 8, 2017
  8. Jacob KellerFeb 8, 2017
  9. Samuel LijinFeb 8, 2017
  10. Cornelius WeigFeb 7, 2017

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.