From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Antonin Delpeuch <antonin@delpeuch.eu>,
Antonin Delpeuch via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: [PATCH] merge-file: warn for implicit 'myers' algorithm
Date: Fri, 05 Jul 2024 23:06:48 -0700 [thread overview]
Message-ID: <xmqqed873vgn.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BEspjHqNXSAwptgxP059qOFU6MzwAd23-893Nw99ft_Ew@mail.gmail.com> (Elijah Newren's message of "Fri, 5 Jul 2024 10:39:46 -0700")
Elijah Newren <newren@gmail.com> writes:
> The previous discussions felt to me like we were moving towards
> consensus, but while I found that encouraging since I think histogram
> would eventually be a better default, I did not make any actual
> proposals and try to push further towards consensus because there are
> a couple known issues that I think should be fixed before we consider
> flipping the default.
OK.
> I have some work-in-progress that was put on
> the backburner a few years ago that I would like to pick up again, and
> if successful, investigate how much that helps general cases in a
> format that can help people make educated decisions, and then again
> float the idea of changing the default.
Sounds like a good plan.
> If consensus is reached, then
> we'd change the default across the board -- diff/log/merge-file/etc.
> rather than just the somewhat rarely used merge-file.
Everybody uses diff.c::diff_algorithm somehow, will be affected by
the diff.algorithm configuration variable, and everybody should
honor "--diff-algorithm=<choice>" command line option to override?
It sounds like a great plan. If ort for some reason performs better
with histogram while format-patch works better with minimal, we
could extend the configuration system to make diff.<cmd>.algorithm
override the more generic diff.algorithm and do similarly silly
things. We may want to also teach the diff plumbing commands to
ignore diff.algorithm for better reproducibility but we may need to
wait for Git 3.0 to do that.
> At least,
> that's my current plan in this area; if others think I should
> investigate things in a different order or would like to see
> additional steps planned into this journey, please do let me know.
Thanks.
next prev parent reply other threads:[~2024-07-06 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 14:21 [PATCH] merge-file: warn for implicit 'myers' algorithm Antonin Delpeuch via GitGitGadget
2024-07-03 17:30 ` Junio C Hamano
2024-07-03 18:28 ` Antonin Delpeuch
2024-07-03 20:19 ` Junio C Hamano
2024-07-05 17:39 ` Elijah Newren
2024-07-05 20:14 ` Antonin Delpeuch
2024-07-06 6:06 ` Junio C Hamano [this message]
2024-07-06 13:30 ` Antonin Delpeuch
2024-07-06 18:06 ` 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=xmqqed873vgn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=antonin@delpeuch.eu \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@gmail.com \
--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 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 NNTP newsgroup(s).