From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2026, #03)
Date: Thu, 11 Jun 2026 16:26:22 +0100 [thread overview]
Message-ID: <3f10ac4d-45d1-4ae1-9079-17d7b52cc7e1@gmail.com> (raw)
In-Reply-To: <xmqqzf14tttx.fsf@gitster.g>
Hi Junio
On 09/06/2026 01:56, Junio C Hamano wrote:
>
> * pw/status-rebase-todo (2026-05-01) 2 commits
> - status: improve rebase todo list parsing
> - sequencer: factor out parsing of todo commands
>
> The display of the rebase todo list in "git status" has been
> improved to correctly abbreviate object IDs for more commands and
> avoid misinterpreting refs as object IDs.
>
> Waiting for response(s) to review comment(s).
> cf. <xmqqbjdwcsno.fsf@gitster.g>
I replied to that message with
<4fafee2c-4151-45f4-a842-17d6b77d951c@gmail.com> I'm waiting to hear
whether you agree that the unambiguous label case is unlikely enough to
happen that we can ignore it.
Thanks
Phillip
next prev parent reply other threads:[~2026-06-11 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 0:56 What's cooking in git.git (Jun 2026, #03) Junio C Hamano
2026-06-11 15:26 ` Phillip Wood [this message]
2026-06-11 16:10 ` 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=3f10ac4d-45d1-4ae1-9079-17d7b52cc7e1@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
/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