From: "Rubén Justo" <rjusto@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2023, #01; Wed, 2)
Date: Mon, 7 Aug 2023 22:59:07 +0200 [thread overview]
Message-ID: <870d6901-e1ea-98fb-96fc-fd568bd35f16@gmail.com> (raw)
In-Reply-To: <xmqqfs518gdh.fsf@gitster.g>
On 2/8/23 20:10, Junio C Hamano wrote:
> * rj/status-bisect-while-rebase (2023-08-01) 1 commit
> - status: fix branch shown when not only bisecting
>
> "git status" is taught to show both the branch being bisected and
> being rebased when both are in effect at the same time.
Maybe this suggest that something has been added, but only fixed.
Perhaps we can say something like:
"git status" was not showing accurate information when bisect and
other operation are in effect at the same time.
>
> Needs review.
> source: <48745298-f12b-8efb-4e48-90d2c22a8349@gmail.com>
Thanks.
next prev parent reply other threads:[~2023-08-07 21:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 18:10 What's cooking in git.git (Aug 2023, #01; Wed, 2) Junio C Hamano
2023-08-02 19:09 ` jt/path-filter-fix (was: Re: What's cooking in git.git (Aug 2023, #01; Wed, 2)) Taylor Blau
2023-08-02 19:20 ` jt/path-filter-fix Junio C Hamano
2023-08-02 19:28 ` jt/path-filter-fix Taylor Blau
[not found] ` <CAP8UFD1vuB2kRr890B7GXum9HAMjRep86zy2tE4yE2C3W5QGHA@mail.gmail.com>
2023-08-07 12:41 ` What's cooking in git.git (Aug 2023, #01; Wed, 2) Christian Couder
2023-08-07 16:19 ` Junio C Hamano
2023-08-07 16:22 ` Taylor Blau
2023-08-07 16:56 ` Elijah Newren
2023-08-17 13:21 ` Johannes Schindelin
2023-08-07 20:59 ` Rubén Justo [this message]
2023-08-08 19:22 ` leak in jt/path-filter-fix, was " Jeff King
2023-08-08 19:25 ` Jeff King
2023-08-08 20:22 ` Taylor Blau
2023-08-08 21:19 ` Jeff King
2023-08-11 22:15 ` Jonathan Tan
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=870d6901-e1ea-98fb-96fc-fd568bd35f16@gmail.com \
--to=rjusto@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.