From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>,
Ezekiel Newren <ezekielnewren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] xdiff: Remove unneeded members from xrecord_t and xdlclass_t
Date: Tue, 10 Feb 2026 12:39:28 -0800 [thread overview]
Message-ID: <xmqqikc4xri7.fsf@gitster.g> (raw)
In-Reply-To: <xmqqtsw8i8fa.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 26 Jan 2026 09:35:21 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Phillip Wood <phillip.wood123@gmail.com> writes:
>
>> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>>
>> This series has a couple of cleanups on top of 'en/xdiff-cleanup-2'
>> that reduce the sizes of the xrecord_t and xdlclass_t. Unfortunately
>> they conflict with 'en/xdiff-cleanup-3' in seen, in particular with
>> db8a50ca6b9 (xdiff: don't waste time guessing the number of lines,
>> 2026-01-02). I'm not particularly convinced that moving the call to
>> xdl_classify_record() out of xdl_prepare_ctx() in that commit is
>> a good idea, but if we decide that we do want to stop classifying
>> lines in xdl_prepare_ctx() we can start passing the hashes out in a
>> separate array rather than wasting space in xrecord_t.
>
> Both patches look well reasoned and sensible.
I was hoping that these two patches will get reviewed by somebody
else in adddition to mine, but unfortunately nothing happened. I am
inclined to merge it down so that the other topic can have a stable
base to be rebased.
Opinions?
prev parent reply other threads:[~2026-02-10 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 10:48 [PATCH 0/2] xdiff: Remove unneeded members from xrecord_t and xdlclass_t Phillip Wood
2026-01-26 10:48 ` [PATCH 1/2] xdiff: remove "line_hash" field from xrecord_t Phillip Wood
2026-01-26 10:48 ` [PATCH 2/2] xdiff: remove unused data from xdlclass_t Phillip Wood
2026-01-26 17:35 ` [PATCH 0/2] xdiff: Remove unneeded members from xrecord_t and xdlclass_t Junio C Hamano
2026-02-10 20:39 ` Junio C Hamano [this message]
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=xmqqikc4xri7.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ezekielnewren@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@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 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.