From: Junio C Hamano <gitster@pobox.com>
To: Git List <git@vger.kernel.org>
Cc: "Rubén Justo" <rjusto@gmail.com>
Subject: Re: [PATCH] status: fix branch shown when not only bisecting
Date: Tue, 15 Aug 2023 21:24:13 -0700 [thread overview]
Message-ID: <xmqq1qg3haxe.fsf@gitster.g> (raw)
In-Reply-To: xmqqtttia3vn.fsf@gitster.g
Junio C Hamano <gitster@pobox.com> writes:
> I didn't see if the proposed output from the command makes sense
> (yet), but somebody else may already have done so and writing their
> reviews on their findings. Let's see if we get any positive reviews
> and move it to 'next' after that.
And unfortunately nothing has happened. Granted that summer in the
northern hemisphere is a slow season, but it is a bit disappointing.
next prev parent reply other threads:[~2023-08-16 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 1:07 [PATCH] status: fix branch shown when not only bisecting Rubén Justo
2023-07-31 23:45 ` Junio C Hamano
2023-08-01 20:39 ` Rubén Justo
2023-08-01 20:45 ` Junio C Hamano
2023-08-16 4:24 ` Junio C Hamano [this message]
2023-09-09 20:12 ` [PATCH v2] " Rubén Justo
2023-10-16 22:08 ` 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=xmqq1qg3haxe.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rjusto@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).