public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Yee Cheng Chin <ychin.git@gmail•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: Yee Cheng Chin via GitGitGadget <gitgitgadget@gmail•com>,
	git@vger•kernel.org
Subject: Re: [PATCH] xdiff: optimize patience diff's LCS search
Date: Wed, 26 Nov 2025 15:15:54 -0500	[thread overview]
Message-ID: <CAHTeOx_4WSLHJDixkshN-e2pqMS6e2qMKnW25x8ed+GOQBvj3g@mail.gmail.com> (raw)
In-Reply-To: <xmqqy0nsmxvt.fsf@gitster.g>

Thanks. I was personally surprised how this simple check ends up
bypassing the slow path almost completely in most situations.

I just noticed I made a typo in the commit message (misspelled
"pytorch"), and will prepare a v2 with the fixed typo.

next prev parent reply	other threads:[~2025-11-26 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 10:25 [PATCH] xdiff: optimize patience diff's LCS search Yee Cheng Chin via GitGitGadget
2025-11-26 18:50 ` Junio C Hamano
2025-11-26 20:15   ` Yee Cheng Chin [this message]
2025-11-27  2:16 ` [PATCH v2] " Yee Cheng Chin via GitGitGadget

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=CAHTeOx_4WSLHJDixkshN-e2pqMS6e2qMKnW25x8ed+GOQBvj3g@mail.gmail.com \
    --to=ychin.git@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitgitgadget@gmail$(echo .)com \
    --cc=gitster@pobox$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox