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

Re: [PATCH v2] status: reword message for a missing upstream branch

From
Elia Pinto <gitter.spiros@gmail.com>
Date
Oct 30, 2026, 09:05 UTC
Message-ID
<20261030090545.9744-1-gitter.spiros@gmail.com>
In-Reply-To
<20261021072137.258934-1-gitter.spiros@gmail.com>
Hi,

a gentle ping on this one. It is queued in 'seen' as ep/status-missing-upstream and has been marked "Needs review" in the last three issues of "What's cooking".

To recap: after cloning an empty repository, "git status" says that the upstream "is gone" and suggests "git branch --unset-upstream", while the upstream was simply never created and "git push" is what the user needs. The patch rewords the message for a configured upstream that does not exist, and suggests "git push" only when it would actually create it (i.e. when @{push} is the upstream).

v2 also addresses Junio's note on v1 about the "[gone]" label: the log message now says correctly where it is translated, and rewording the label itself is left for a separate patch.

Any review or comment would be appreciated.

Thanks, Elia

Previous: Elia PintoNext: Elia Pinto
Message 6 of 14 in “status: reword message for a missing upstream branch”
  1. status: reword message for a missing upstream branchElia Pinto, Oct 19, 2026
  2. Harald NordgrenOct 19, 2026
  3. Junio C HamanoOct 19, 2026
  4. Elia PintoOct 20, 2026
  5. status: reword message for a missing upstream branchElia Pinto, Oct 21, 2026
  6. Elia PintoOct 30, 2026
  7. Elia PintoNov 17, 2026
  8. Harald NordgrenNov 17, 2026
  9. Junio C HamanoNov 17, 2026
  10. Junio C HamanoNov 18, 2026
  11. Elia PintoNov 19, 2026
  12. Junio C HamanoNov 19, 2026
  13. status: reword message for a missing upstream branchElia Pinto, Nov 19, 2026
  14. Junio C HamanoNov 19, 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.