From: John Cai <johncai86@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: "John Cai via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Eric Sunshine" <sunshine@sunshineco.com>,
"Phillip Wood" <phillip.wood123@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jeff King" <peff@peff.net>
Subject: Re: [PATCH v3 2/2] diff: teach diff to read algorithm from diff driver
Date: Mon, 20 Feb 2023 10:32:52 -0500 [thread overview]
Message-ID: <EE7565DF-BE70-4C45-AF0B-95C85050DFA4@gmail.com> (raw)
In-Reply-To: <CABPp-BFCMpA=nHtb5RuQL7ACbkhSEKtvmRxKwMuktcf24uQJtQ@mail.gmail.com>
Hi Elijah,
On 17 Feb 2023, at 21:56, Elijah Newren wrote:
> On Fri, Feb 17, 2023 at 12:21 PM John Cai via GitGitGadget
> <gitgitgadget@gmail.com> wrote:
>>
>> From: John Cai <johncai86@gmail.com>
>>
>> It can be useful to specify diff algorithms per file type. For example,
>> one may want to use the minimal diff algorithm for .json files, another
>> for .c files, etc.
>>
>> The diff machinery already checks attributes for a diff driver. Teach
>> the diff driver parser a new type "algorithm" to look for in the
>> config, which will be used if a driver has been specified through the
>> attributes.
>>
>> Enforce precedence of the diff algorithm by favoring the command line
>> option, then looking at the driver attributes & config combination, then
>> finally the diff.algorithm config.
>>
>> To enforce precedence order, use a new `ignore_driver_algorithm` member
>> during options pasing to indicate the diff algorithm was set via command
>> line args.
>
> s/pasing/parsing/
thanks for noticing this!
>
>> Signed-off-by: John Cai <johncai86@gmail.com>
>> ---
>> Documentation/gitattributes.txt | 37 ++++++++++++++++++++++++++++++++
>> diff.c | 33 ++++++++++++++++++++--------
>> diff.h | 1 +
>> t/lib-diff-alternative.sh | 38 ++++++++++++++++++++++++++++++++-
>> userdiff.c | 4 +++-
>> userdiff.h | 1 +
>> 6 files changed, 103 insertions(+), 11 deletions(-)
>>
>> diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
>> index c19e64ea0ef..f212079a131 100644
>> --- a/Documentation/gitattributes.txt
>> +++ b/Documentation/gitattributes.txt
>> @@ -758,6 +758,43 @@ with the above configuration, i.e. `j-c-diff`, with 7
>> parameters, just like `GIT_EXTERNAL_DIFF` program is called.
>> See linkgit:git[1] for details.
>>
>> +Setting the internal diff algorithm
>> +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> +
>> +The diff algorithm can be set through the `diff.algorithm` config key, but
>> +sometimes it may be helpful to set the diff algorithm by path. For example, one
>> +might wish to set a diff algorithm automatically for all `.json` files such that
>> +the user would not need to pass in a separate command line `--diff-algorithm`
>> +flag each time.
>> +
>> +First, in `.gitattributes`, assign the `diff` attribute for paths.
>> +
>> +------------------------
>> +*.json diff=<name>
>> +------------------------
>> +
>> +Then, define a "diff.<name>.algorithm" configuration to specify the diff
>
> Should there be a link to `git-config` right after "configuration"?
> Otherwise, users may think that they are being told to specify
> additional configuration within the .gitattributes file.
>
>> +algorithm, choosing from `meyers`, `patience`, `minimal`, or `histogram`.
>
> s/meyers/myers/
likewise.
>
>> +
>> +----------------------------------------------------------------
>> +[diff "<name>"]
>> + algorithm = histogram
>> +----------------------------------------------------------------
>
> It's pretty easy to assume the above is meant to be part of the
> .gitattributes file instead of the .git/config file. Don't most users
> run `git config` commands directly rather than edit the .git/config
> file? Should we provide a sample command rather than showing what the
> config file will contain?
Not sure--I think I was was just following what I saw in the existing
documentation for driver configuration. But would be interested to see what
other folks think.
>
>> +
>> +This diff algorithm applies to user facing diff output like git-diff(1),
>> +git-show(1) and is used for the `--stat` output as well. The merge machinery
>> +will not use the diff algorithm set through this method.
>
> Yaay, thanks for including this!
>
>
> I'm still curious if this should this also include warnings/caveats, such as:
> * The diff attribute specified in .gitattributes will be ignored in
> a bare clone
> * The diff attribute specified in .gitattributes will be ignored if
> it is only specified in another branch (e.g. on a branch "special-file
> diff=patience" recorded in .gitattributes, then checkout master but
> run `git log -1 -p $branch`)
> * When a file is renamed, the diff attribute for the pre-image name
> is the only one the system pays attention to (thus adding "-R" can
> flip which diff algorithm is run for the renamed file).
I would be fine with adding that--though originally I was thinking that these
can be inferred from the way that gitattributes are documented in [1]. Calling
these out would make it more clear though, so I could go either way.
>
> Also, since I tested the three items above to verify they are valid
> warnings, I'm a bit confused. I thought your intent was to use this
> server-side[1], so isn't the bare clone aspect a deal-breaker for your
> intended usecase?
>
> [1] https://lore.kernel.org/git/7852AC7B-7A4E-4DD0-ADEA-CFFD5D16C595@gmail.com/
yes, indeed. I was planning on adding bare repository support in a separate
patch series, since the additions in [2] allows .gitattributes to be read from a
bare repository.
1. https://git-scm.com/docs/gitattributes
2. https://lore.kernel.org/git/0ca8b2458921fc40269b0c43b5ec86eba77d6b54.1673684790.git.karthik.188@gmail.com/
thanks!
John
>
>> +
>> +NOTE: If the `command` key also exists, then Git will treat this as an external
>> +diff and attempt to use the value set for `command` as an external program. For
>> +instance, the following config, combined with the above `.gitattributes` file,
>> +will result in `command` favored over `algorithm`.
>> +
>> +----------------------------------------------------------------
>> +[diff "<name>"]
>> + command = j-c-diff
>> + algorithm = histogram
>> +----------------------------------------------------------------
>>
>> Defining a custom hunk-header
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> diff --git a/diff.c b/diff.c
>> index 5efc22ca06b..04469da6d34 100644
>> --- a/diff.c
>> +++ b/diff.c
>> @@ -4456,15 +4456,13 @@ static void run_diff_cmd(const char *pgm,
>> const char *xfrm_msg = NULL;
>> int complete_rewrite = (p->status == DIFF_STATUS_MODIFIED) && p->score;
>> int must_show_header = 0;
>> + struct userdiff_driver *drv = NULL;
>>
>> -
>> - if (o->flags.allow_external) {
>> - struct userdiff_driver *drv;
>> -
>> + if (o->flags.allow_external || !o->ignore_driver_algorithm)
>> drv = userdiff_find_by_path(o->repo->index, attr_path);
>> - if (drv && drv->external)
>> - pgm = drv->external;
>> - }
>> +
>> + if (o->flags.allow_external && drv && drv->external)
>> + pgm = drv->external;
>>
>> if (msg) {
>> /*
>> @@ -4481,12 +4479,16 @@ static void run_diff_cmd(const char *pgm,
>> run_external_diff(pgm, name, other, one, two, xfrm_msg, o);
>> return;
>> }
>> - if (one && two)
>> + if (one && two) {
>> + if (drv && !o->ignore_driver_algorithm && drv->algorithm)
>> + set_diff_algorithm(o, drv->algorithm);
>> +
>> builtin_diff(name, other ? other : name,
>> one, two, xfrm_msg, must_show_header,
>> o, complete_rewrite);
>> - else
>> + } else {
>> fprintf(o->file, "* Unmerged path %s\n", name);
>> + }
>> }
>>
>> static void diff_fill_oid_info(struct diff_filespec *one, struct index_state *istate)
>> @@ -4583,6 +4585,14 @@ static void run_diffstat(struct diff_filepair *p, struct diff_options *o,
>> const char *name;
>> const char *other;
>>
>> + if (!o->ignore_driver_algorithm) {
>> + struct userdiff_driver *drv = userdiff_find_by_path(o->repo->index, p->one->path);
>> +
>> + if (drv && drv->algorithm) {
>> + set_diff_algorithm(o, drv->algorithm);
>> + }
>> + }
>> +
>> if (DIFF_PAIR_UNMERGED(p)) {
>> /* unmerged */
>> builtin_diffstat(p->one->path, NULL, NULL, NULL,
>> @@ -5130,6 +5140,8 @@ static int diff_opt_diff_algorithm(const struct option *opt,
>> return error(_("option diff-algorithm accepts \"myers\", "
>> "\"minimal\", \"patience\" and \"histogram\""));
>>
>> + options->ignore_driver_algorithm = 1;
>> +
>> return 0;
>> }
>>
>> @@ -5145,6 +5157,8 @@ static int diff_opt_diff_algorithm_no_arg(const struct option *opt,
>> BUG("available diff algorithms include \"myers\", "
>> "\"minimal\", \"patience\" and \"histogram\"");
>>
>> + options->ignore_driver_algorithm = 1;
>> +
>> return 0;
>> }
>>
>> @@ -5285,6 +5299,7 @@ static int diff_opt_patience(const struct option *opt,
>> for (i = 0; i < options->anchors_nr; i++)
>> free(options->anchors[i]);
>> options->anchors_nr = 0;
>> + options->ignore_driver_algorithm = 1;
>>
>> return set_diff_algorithm(options, "patience");
>> }
>> diff --git a/diff.h b/diff.h
>> index 41eb2c3d428..8d770b1d579 100644
>> --- a/diff.h
>> +++ b/diff.h
>> @@ -333,6 +333,7 @@ struct diff_options {
>> int prefix_length;
>> const char *stat_sep;
>> int xdl_opts;
>> + int ignore_driver_algorithm;
>>
>> /* see Documentation/diff-options.txt */
>> char **anchors;
>> diff --git a/t/lib-diff-alternative.sh b/t/lib-diff-alternative.sh
>> index 8d1e408bb58..2dc02bca873 100644
>> --- a/t/lib-diff-alternative.sh
>> +++ b/t/lib-diff-alternative.sh
>> @@ -105,10 +105,46 @@ index $file1..$file2 100644
>> }
>> EOF
>>
>> + cat >expect_diffstat <<EOF
>> + file1 => file2 | 21 ++++++++++-----------
>> + 1 file changed, 10 insertions(+), 11 deletions(-)
>> +EOF
>> +
>> STRATEGY=$1
>>
>> + test_expect_success "$STRATEGY diff from attributes" '
>> + echo "file* diff=driver" >.gitattributes &&
>> + git config diff.driver.algorithm "$STRATEGY" &&
>> + test_must_fail git diff --no-index file1 file2 > output &&
>> + cat expect &&
>> + cat output &&
>> + test_cmp expect output
>> + '
>> +
>> + test_expect_success "$STRATEGY diff from attributes has valid diffstat" '
>> + echo "file* diff=driver" >.gitattributes &&
>> + git config diff.driver.algorithm "$STRATEGY" &&
>> + test_must_fail git diff --stat --no-index file1 file2 > output &&
>> + test_cmp expect_diffstat output
>> + '
>> +
>> test_expect_success "$STRATEGY diff" '
>> - test_must_fail git diff --no-index "--$STRATEGY" file1 file2 > output &&
>> + test_must_fail git diff --no-index "--diff-algorithm=$STRATEGY" file1 file2 > output &&
>> + test_cmp expect output
>> + '
>> +
>> + test_expect_success "$STRATEGY diff command line precedence before attributes" '
>> + echo "file* diff=driver" >.gitattributes &&
>> + git config diff.driver.algorithm meyers &&
>
> Is this misspelling of myers intentional? I think with the typo, the
> code falls back to the default algorithm, which happens to be myers,
> so I think the test works either way, but were you intending to test
> fallback behavior in case of a typo here, or was that accidental?
>
>
>
>> + test_must_fail git diff --no-index "--diff-algorithm=$STRATEGY" file1 file2 > output &&
>> + test_cmp expect output
>> + '
>> +
>> + test_expect_success "$STRATEGY diff attributes precedence before config" '
>> + git config diff.algorithm default &&
>> + echo "file* diff=driver" >.gitattributes &&
>> + git config diff.driver.algorithm "$STRATEGY" &&
>> + test_must_fail git diff --no-index file1 file2 > output &&
>> test_cmp expect output
>> '
>>
>> diff --git a/userdiff.c b/userdiff.c
>> index d71b82feb74..ff25cfc4b4c 100644
>> --- a/userdiff.c
>> +++ b/userdiff.c
>> @@ -293,7 +293,7 @@ PATTERNS("scheme",
>> "|([^][)(}{[ \t])+"),
>> PATTERNS("tex", "^(\\\\((sub)*section|chapter|part)\\*{0,1}\\{.*)$",
>> "\\\\[a-zA-Z@]+|\\\\.|[a-zA-Z0-9\x80-\xff]+"),
>> -{ "default", NULL, -1, { NULL, 0 } },
>> +{ "default", NULL, NULL, -1, { NULL, 0 } },
>> };
>> #undef PATTERNS
>> #undef IPATTERN
>> @@ -394,6 +394,8 @@ int userdiff_config(const char *k, const char *v)
>> return parse_bool(&drv->textconv_want_cache, k, v);
>> if (!strcmp(type, "wordregex"))
>> return git_config_string(&drv->word_regex, k, v);
>> + if (!strcmp(type, "algorithm"))
>> + return git_config_string(&drv->algorithm, k, v);
>>
>> return 0;
>> }
>> diff --git a/userdiff.h b/userdiff.h
>> index aee91bc77e6..24419db6973 100644
>> --- a/userdiff.h
>> +++ b/userdiff.h
>> @@ -14,6 +14,7 @@ struct userdiff_funcname {
>> struct userdiff_driver {
>> const char *name;
>> const char *external;
>> + const char *algorithm;
>> int binary;
>> struct userdiff_funcname funcname;
>> const char *word_regex;
>> --
>> gitgitgadget
next prev parent reply other threads:[~2023-02-20 15:33 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 3:46 [PATCH 0/2] Teach diff to honor diff algorithms set through git attributes John Cai via GitGitGadget
2023-02-05 3:46 ` [PATCH 1/2] diff: consolidate diff algorithm option parsing John Cai via GitGitGadget
2023-02-06 16:20 ` Phillip Wood
2023-02-05 3:46 ` [PATCH 2/2] diff: teach diff to read gitattribute diff-algorithm John Cai via GitGitGadget
2023-02-05 17:50 ` Eric Sunshine
2023-02-06 13:10 ` John Cai
2023-02-06 16:27 ` Phillip Wood
2023-02-06 18:14 ` Eric Sunshine
2023-02-06 19:50 ` John Cai
2023-02-09 8:26 ` Elijah Newren
2023-02-09 10:31 ` "bad" diffs (was: [PATCH 2/2] diff: teach diff to read gitattribute diff-algorithm) Ævar Arnfjörð Bjarmason
2023-02-09 16:37 ` [PATCH 2/2] diff: teach diff to read gitattribute diff-algorithm John Cai
2023-02-06 16:39 ` Ævar Arnfjörð Bjarmason
2023-02-06 20:37 ` John Cai
2023-02-07 14:55 ` Phillip Wood
2023-02-07 17:00 ` John Cai
2023-02-09 9:09 ` Elijah Newren
2023-02-09 14:44 ` Phillip Wood
2023-02-10 9:57 ` Elijah Newren
2023-02-11 17:39 ` Phillip Wood
2023-02-11 1:59 ` Jeff King
2023-02-15 2:35 ` Elijah Newren
2023-02-15 4:21 ` Jeff King
2023-02-15 5:20 ` Junio C Hamano
2023-02-15 14:44 ` Phillip Wood
2023-02-15 15:00 ` Jeff King
2023-02-07 17:27 ` Ævar Arnfjörð Bjarmason
2023-02-15 14:47 ` Phillip Wood
2023-02-09 8:44 ` Elijah Newren
2023-02-14 21:16 ` John Cai
2023-02-15 3:41 ` Elijah Newren
2023-02-09 7:50 ` Elijah Newren
2023-02-09 9:41 ` Ævar Arnfjörð Bjarmason
2023-02-11 2:04 ` Jeff King
2023-02-07 17:56 ` Jeff King
2023-02-07 20:18 ` Ævar Arnfjörð Bjarmason
2023-02-07 20:47 ` Junio C Hamano
2023-02-07 21:05 ` Ævar Arnfjörð Bjarmason
2023-02-07 21:28 ` Junio C Hamano
2023-02-07 21:44 ` Ævar Arnfjörð Bjarmason
2023-02-09 16:34 ` John Cai
2023-02-11 1:39 ` Jeff King
2023-02-14 21:40 ` [PATCH v2 0/2] Teach diff to honor diff algorithms set through git attributes John Cai via GitGitGadget
2023-02-14 21:40 ` [PATCH v2 1/2] diff: consolidate diff algorithm option parsing John Cai via GitGitGadget
2023-02-15 2:38 ` Junio C Hamano
2023-02-15 23:34 ` John Cai
2023-02-15 23:42 ` Junio C Hamano
2023-02-16 2:14 ` Jeff King
2023-02-16 2:57 ` Junio C Hamano
2023-02-16 20:34 ` John Cai
2023-02-14 21:40 ` [PATCH v2 2/2] diff: teach diff to read gitattribute diff-algorithm John Cai via GitGitGadget
2023-02-15 2:56 ` Junio C Hamano
2023-02-15 3:20 ` Junio C Hamano
2023-02-16 20:37 ` John Cai
2023-02-17 20:21 ` [PATCH v3 0/2] Teach diff to honor diff algorithms set through git attributes John Cai via GitGitGadget
2023-02-17 20:21 ` [PATCH v3 1/2] diff: consolidate diff algorithm option parsing John Cai via GitGitGadget
2023-02-17 21:27 ` Junio C Hamano
2023-02-18 1:36 ` Elijah Newren
2023-02-17 20:21 ` [PATCH v3 2/2] diff: teach diff to read algorithm from diff driver John Cai via GitGitGadget
2023-02-17 21:50 ` Junio C Hamano
2023-02-18 2:56 ` Elijah Newren
2023-02-20 15:32 ` John Cai [this message]
2023-02-20 16:21 ` Elijah Newren
2023-02-20 16:49 ` John Cai
2023-02-20 17:32 ` Elijah Newren
2023-02-20 20:53 ` John Cai
2023-02-22 19:47 ` Jeff King
2023-02-24 17:44 ` John Cai
2023-02-18 1:16 ` [PATCH v3 0/2] Teach diff to honor diff algorithms set through git attributes Elijah Newren
2023-02-20 13:37 ` John Cai
2023-02-20 21:04 ` [PATCH v4 " John Cai via GitGitGadget
2023-02-20 21:04 ` [PATCH v4 1/2] diff: consolidate diff algorithm option parsing John Cai via GitGitGadget
2023-02-20 21:04 ` [PATCH v4 2/2] diff: teach diff to read algorithm from diff driver John Cai via GitGitGadget
2023-02-21 17:34 ` [PATCH v4 0/2] Teach diff to honor diff algorithms set through git attributes Junio C Hamano
2023-02-21 18:05 ` Elijah Newren
2023-02-21 18:51 ` Junio C Hamano
2023-02-21 19:36 ` John Cai
2023-02-21 20:16 ` Elijah Newren
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=EE7565DF-BE70-4C45-AF0B-95C85050DFA4@gmail.com \
--to=johncai86@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=phillip.wood123@gmail.com \
--cc=sunshine@sunshineco.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).