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 (May 2026, #01)
Date: Mon, 4 May 2026 14:16:44 +0100 [thread overview]
Message-ID: <ef949395-53b4-4799-a031-fcedfacc8824@gmail.com> (raw)
In-Reply-To: <xmqqmryhtar8.fsf@gitster.g>
On 03/05/2026 04:47, Junio C Hamano wrote:
>
> * rs/grep-column-only-match-fix (2026-04-24) 1 commit
> - grep: fix --column --only-match for 2nd and later matches
>
> "git grep" update.
>
> Will merge to 'next'?
> source: <9bd69678-f04b-41d2-ad74-a386820d34c8@web.de>
I've just read this patch and it looked good. It is surprising no one
has complained about the strange column numbers before
> * hn/git-checkout-m-with-stash (2026-04-28) 5 commits
> - checkout -m: autostash when switching branches
> - checkout: rollback lock on early returns in merge_working_tree
> - sequencer: teach autostash apply to take optional conflict marker labels
> - sequencer: allow create_autostash to run silently
> - stash: add --label-ours, --label-theirs, --label-base for apply
>
> "git checkout -m another-branch" was invented to deal with local
> changes to paths that are different between the current and the new
> branch, but it gave only one chance to resolve conflicts. The command
> was taught to create a stash to save the local changes.
>
> Will merge to 'next'?
> source: <pull.2234.v16.git.git.1777401552.gitgitgadget@gmail.com>
I'm happy with the latest re-roll - this looks ready to me
> * pw/xdiff-shrink-memory-consumption (2026-04-02) 4 commits
> . xdiff: reduce the size of array
> . xprepare: simplify error handling
> . xdiff: cleanup xdl_clean_mmatch()
> . xdiff: reduce size of action arrays
>
> Shrink wasted memory in Myers diff that does not account for common
> prefix and suffix removal.
>
> Needs to be rebased on updated en/xdiff-cleanup-3.
Will do
> * en/xdiff-cleanup-3 (2026-04-29) 6 commits
> - xdiff/xdl_cleanup_records: make execution of action easier to follow
> - xdiff/xdl_cleanup_records: make setting action easier to follow
> - xdiff/xdl_cleanup_records: make limits more clear
> - xdiff/xdl_cleanup_records: use unambiguous types
> - xdiff: use unambiguous types in xdl_bogo_sqrt()
> - xdiff/xdl_cleanup_records: delete local recs pointer
>
> Preparation of the xdiff/ codebase to work with Rust.
>
> Will merge to 'next'?
Yes, I think this is ready as well
Thanks
Phillip
next prev parent reply other threads:[~2026-05-04 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 3:47 What's cooking in git.git (May 2026, #01) Junio C Hamano
2026-05-04 13:16 ` Phillip Wood [this message]
2026-05-04 14:18 ` Patrick Steinhardt
2026-05-04 17:44 ` Karthik Nayak
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=ef949395-53b4-4799-a031-fcedfacc8824@gmail.com \
--to=phillip.wood123@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox