From: Elia Pinto <gitter.spiros@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, haraldnordgren@gmail.com,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH v2] status: reword message for a missing upstream branch
Date: Fri, 30 Oct 2026 10:05:45 +0100 [thread overview]
Message-ID: <20261030090545.9744-1-gitter.spiros@gmail.com> (raw)
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
next prev parent reply other threads:[~2026-10-30 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 17:57 [PATCH] status: reword message for a missing upstream branch Elia Pinto
2026-10-19 18:04 ` Harald Nordgren
2026-10-19 21:42 ` Junio C Hamano
2026-10-20 7:29 ` Elia Pinto
2026-10-21 7:21 ` [PATCH v2] " Elia Pinto
2026-10-30 9:05 ` Elia Pinto [this message]
2026-11-17 21:27 ` Elia Pinto
2026-11-17 22:03 ` Harald Nordgren
2026-11-17 23:29 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261030090545.9744-1-gitter.spiros@gmail.com \
--to=gitter.spiros@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=haraldnordgren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox