From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Harald Nordgren <haraldnordgren@gmail.com>
Subject: Re: What's cooking in git.git (Jul 2026, #12)
Date: Wed, 29 Jul 2026 16:20:56 +0100 [thread overview]
Message-ID: <414ebe62-c7f6-4d44-bde2-b689e35accfc@gmail.com> (raw)
In-Reply-To: <xmqq1pclc210.fsf@gitster.g>
On 29/07/2026 15:18, Junio C Hamano wrote:
> Phillip Wood <phillip.wood123@gmail.com> writes:
>
>>> The experimental 'git history' command has been taught a new 'squash'
>>> subcommand to fold a range of commits into a single commit, with any
>>> descendants replayed on top.
>>>
>>> Will merge to 'master'.
>>> cf. <DK1KIF2OI8IF.11188A3YEQV1C@lfurio.us>
>>> cf. <DK1KIH6CXW0X.1U2V3GU8L6HB7@lfurio.us>
>>> source: <pull.2337.v10.git.git.1784536024.gitgitgadget@gmail.com>
>>
>> Oh, I'd missed this going into master. Has the implementation received
>> any serious review? I've seen messages from a couple of people trying it
>> out but I can't see anybody reading the code.
>
> Thanks for stopping me. I am happy to immediately revert the merge
> of this topic into 'next'.
>
> Perhaps I should re-evaluate the "What's Cooking" report and eject
> other topics from 'next' as well. There are indeed topics I did not
> personally read, relying instead on impressions from busy exchanges
> (including earlier iterations read by others X-<).
>
> Are there other topics in 'next' that do not deserve to be there
> yet?
There aren't any others that I'm aware of, but I've not looked at most
of them so that probably does not mean much.
> I cannot, of course, afford to be the sole serious reviewer and
> merge only those I have carefully read through, given that there are
> only 24 hours in a day and I have other obligations. So either our
> quality criteria must suffer, like this episode showed us, or more
> topics must be ignored.
Yes, we could really do with more reviewers
>> Having a quick look
>> through it assumes the presence of an UNINTERESTING commit means we have
>> a BOTTOM commit. It then assumes that UNINTERESTING commit means we
>> cannot reach any root commits. Both of those assumptions are false I
>> think.
>
> Very true.
>
>> ... I'll try and go through the patches and produce some fixups,
>> though that may not be until next week.
Harald - I've got some half finished fixups that I didn't get round it
finishing when I had a look at this last week that I'll clean up and
send so I'd hold off re-rolling for now.
Thanks
Phillip
next prev parent reply other threads:[~2026-07-29 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 3:09 What's cooking in git.git (Jul 2026, #12) Junio C Hamano
2026-07-29 13:24 ` Phillip Wood
2026-07-29 14:18 ` Junio C Hamano
2026-07-29 15:20 ` Phillip Wood [this message]
2026-07-29 17:48 ` Junio C Hamano
2026-07-29 15:14 ` Phillip Wood
2026-07-29 15:52 ` 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=414ebe62-c7f6-4d44-bde2-b689e35accfc@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=haraldnordgren@gmail.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 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.