Git development
 help / color / mirror / Atom feed
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: Tue, 17 Nov 2026 22:27:56 +0100	[thread overview]
Message-ID: <20261117212756.716005-1-gitter.spiros@gmail.com> (raw)
In-Reply-To: <20261030090545.9744-1-gitter.spiros@gmail.com>

Hi Harald, Junio,

A gentle ping on this v2. It has been queued in 'seen' as
ep/status-missing-upstream, and "What's cooking" has listed it as
"Needs review" for a while. It still merges cleanly with both master
(e1ec09b23c) and 'seen'.

As far as I can tell, v2 addresses the comments Junio made on v1 (the
shorter "missing" he suggested for "[gone]" will come as a separate
patch, as I said in my reply), so what it is missing is a review, but
please tell me if I overlooked something.

Harald, you found the idea sensible when you looked at the RFC; would
you have time to look at v2? (v1 was a resend of the RFC, not a
duplicate, as noted below its "---".)

If something needs to change for this to move forward, I will be happy
to send a v3. If nobody finds the change worth having, that is fine
too: just say so and I will withdraw it, so that it does not linger in
'seen'.

Thanks,
Elia

  reply	other threads:[~2026-11-17 21:28 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
2026-11-17 21:27     ` Elia Pinto [this message]
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=20261117212756.716005-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