From: Phillip Wood <phillip.wood123@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
phillip.wood@dunelm.org.uk
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)
Date: Thu, 9 Dec 2021 10:39:30 +0000 [thread overview]
Message-ID: <4dc6e1ee-bbbb-247b-f9e7-4f8dd37c57ed@gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2112081340420.90@tvgsbejvaqbjf.bet>
Hi Dscho
On 08/12/2021 12:42, Johannes Schindelin wrote:
> Hi Phillip,
>
> On Mon, 6 Dec 2021, Phillip Wood wrote:
>
>> On 04/12/2021 01:37, Junio C Hamano wrote:
>>
>>> * pw/diff-color-moved-fix (2021-10-27) 15 commits
>>> - diff --color-moved: intern strings
>>> - diff: use designated initializers for emitted_diff_symbol
>>> - diff --color-moved-ws=allow-indentation-change: improve hash lookups
>>> - diff --color-moved: stop clearing potential moved blocks
>>> - diff --color-moved: shrink potential moved blocks as we go
>>> - diff --color-moved: unify moved block growth functions
>>> - diff --color-moved: call comparison function directly
>>> - diff --color-moved-ws=allow-indentation-change: simplify and optimize
>>> - diff: simplify allow-indentation-change delta calculation
>>> - diff --color-moved: avoid false short line matches and bad zerba
>>> coloring
>>> - diff --color-moved=zebra: fix alternate coloring
>>> - diff --color-moved: rewind when discarding pmb
>>> - diff --color-moved: factor out function
>>> - diff --color-moved: clear all flags on blocks that are too short
>>> - diff --color-moved: add perf tests
>>>
>>> Long-overdue correctness and performance update to "diff
>>> --color-moved" feature.
>>>
>>> Need to pick up the reroll before merging to 'next'.
>>> cf. <pull.981.v4.git.1637056178.gitgitgadget@gmail.com>
>>
>> Dscho spotted a typo which I was going to correct with a re-roll but I've been
>> holding off in case he has time to read the rest of the series.
>
> I would have loved to give this a much more in-depth review, but the days
> have become short on the North hemisphere, haven't they.
I know, it felt like it never got light here yesterday.
> In any case, the patch series looks good to me (personally, I do not care
> so much about typos as long as they aren't indicator of sloppiness, which
> in this case they aren't, I find your patches really well done).
I've just posted v5 with the typo fixed, thanks for your comments.
Phillip
next prev parent reply other threads:[~2021-12-09 10:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 1:37 What's cooking in git.git (Dec 2021, #01; Fri, 3) Junio C Hamano
2021-12-06 19:13 ` Phillip Wood
2021-12-06 19:24 ` Junio C Hamano
2021-12-08 12:42 ` Johannes Schindelin
2021-12-09 1:02 ` Junio C Hamano
2021-12-09 10:39 ` Phillip Wood [this message]
2021-12-07 6:00 ` en/keep-cwd (Was: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Elijah Newren
2021-12-07 9:17 ` Ævar Arnfjörð Bjarmason
2021-12-07 20:33 ` Elijah Newren
2021-12-07 18:26 ` en/keep-cwd Junio C Hamano
2021-12-08 12:46 ` en/keep-cwd (Was: Re: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Johannes Schindelin
2021-12-07 15:54 ` What's cooking in git.git (Dec 2021, #01; Fri, 3) Derrick Stolee
2021-12-07 19:37 ` cf/fetch-set-upstream-while-detached (was: What's cooking in git.git (Dec 2021, #01; Fri, 3)) Ævar Arnfjörð Bjarmason
2021-12-07 20:41 ` cf/fetch-set-upstream-while-detached Junio C Hamano
2021-12-07 22:04 ` [PATCH v5] pull, fetch: fix segfault in --set-upstream option Ævar Arnfjörð Bjarmason
-- strict thread matches above, loose matches on Subject: below --
2021-12-04 1:37 What's cooking in git.git (Dec 2021, #01; Fri, 3) Junio C Hamano
2021-12-07 1:08 ` Junio C Hamano
2021-12-07 16:21 ` Derrick Stolee
2021-12-07 17:25 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4dc6e1ee-bbbb-247b-f9e7-4f8dd37c57ed@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).