{"thread":{"id":"61200","subject":"[PATCH v3 0/3] Assorted improvements salvaged from an earlier series","startedAt":"2024-03-25T20:34:57Z","lastAt":"2024-04-06T01:49:12Z","messageCount":10,"participants":["Dragan Simic","Eric Sunshine"],"isPatch":true,"patchVersion":3,"patchTotal":3},"messages":[{"id":"491500","messageId":"cover.1711398665.git.dsimic@manjaro.org","threadId":"61200","inReplyTo":null,"subject":"[PATCH v3 0/3] Assorted improvements salvaged from an earlier series","fromName":"Dragan Simic","fromEmail":"dsimic@manjaro.org","sentAt":"2024-03-25T20:34:50Z","receivedAt":"2024-03-25T20:34:57Z","isPatch":true,"sender":{"key":"dsimic@manjaro.org","avatar":null},"body":"This series contains patches salvaged from my earlier series, [1] for\nwhich it has been concluded to be not acceptable for merging, because of\npossible issues with various git scripts. [2]\n\nChanges introduced to the patches are described separately in each patch.\n\nLink to v1: https://lore.kernel.org/git/cover.1710968761.git.dsimic@manjaro.org/T/#u\nLink to v2: https://lore.kernel.org/git/cover.1711302588.git.dsimic@manjaro.org/T/#u\n\n[1] https://lore.kernel.org/git/cover.1710781235.git.dsimic@manjaro.org/T/#u\n[2] https://lore.kernel.org/git/d8475579f014a90b27efaf6207bc6fb0@manjaro.org/\n\nDragan Simic (3):\n grep: perform some minor code and comment cleanups\n grep docs: describe --recurse-submodules further and improve\n formatting a bit\n grep docs: describe --no-index further and improve formatting a bit\n\n Documentation/config/grep.txt | 2 +-\n Documentation/git-grep.txt | 36 +++++++++++++++++++++--------------\n builtin/grep.c | 21 ++++++++------------\n 3 files changed, 31 insertions(+), 28 deletions(-)\n\n"},{"id":"491501","messageId":"55867253d2925892f5192dbc3145f7bc9221b791.1711398665.git.dsimic@manjaro.org","threadId":"61200","inReplyTo":"cover.1711398665.git.dsimic@manjaro.org","subject":"[PATCH v3 1/3] grep: perform some minor code and comment cleanups","fromName":"Dragan Simic","fromEmail":"dsimic@manjaro.org","sentAt":"2024-03-25T20:34:51Z","receivedAt":"2024-03-25T20:34:58Z","isPatch":true,"sender":{"key":"dsimic@manjaro.org","avatar":null},"body":"Move some variable definitions around, and reflow one comment block, to\nmake the code a bit neater after spotting those slightly unpolished areas.\nThere are no functional changes to the source code.\n\nSigned-off-by: Dragan Simic \n---\n\nNotes:\n Changes in v3:\n - No changes were introduced\n \n Changes in v2:\n - No changes were introduced\n \n This patch is salvaged from my earlier series, [1] for which it has been\n concluded to be not acceptable for merging, because of possible issues\n with various git scripts. [2]\n \n Compared to the version in the earlies series, there are no changes in\n this version. As expected and as already discussed, patches like this one\n inevitably raise a few eyebrows. [3][4][5]\n \n [1] https://lore.kernel.org/git/cover.1710781235.git.dsimic@manjaro.org/T/#u\n [2] https://lore.kernel.org/git/d8475579f014a90b27efaf6207bc6fb0@manjaro.org/\n [3] https://lore.kernel.org/git/CAPig+cQ6Y2oOaPkKFsD41beXLHjhD++nmf59xrcswpb6_Q-sdA@mail.gmail.com/\n [4] https://lore.kernel.org/git/xmqqjzlzt61d.fsf@gitster.g/#t\n [5] https://lore.kernel.org/git/24093dca675c49cfde39f6d6efca2342@manjaro.org/\n\n builtin/grep.c | 21 ++++++++-------------\n 1 file changed, 8 insertions(+), 13 deletions(-)\n\ndiff --git a/builtin/grep.c b/builtin/grep.c\nindex 982bcfc4b1df..af89c8b5cb19 100644\n--- a/builtin/grep.c\n+++ b/builtin/grep.c\n@@ -623,13 +623,13 @@ static int grep_tree(struct grep_opt *opt, const struct pathspec *pathspec,\n \t\t struct tree_desc *tree, struct strbuf *base, int tn_len,\n \t\t int check_attr)\n {\n-\tstruct repository *repo = opt->repo;\n-\tint hit = 0;\n+\tint hit = 0, name_base_len = 0;\n+\tint old_baselen = base->len;\n \tenum interesting match = entry_not_interesting;\n+\tstruct repository *repo = opt->repo;\n \tstruct name_entry entry;\n-\tint old_baselen = base->len;\n \tstruct strbuf name = STRBUF_INIT;\n-\tint name_base_len = 0;\n+\n \tif (repo->submodule_prefix) {\n \t\tstrbuf_addstr(&name, repo->submodule_prefix);\n \t\tname_base_len = name.len;\n@@ -890,19 +890,15 @@ static int pattern_callback(const struct option *opt, const char *arg,\n \n int cmd_grep(int argc, const char **argv, const char *prefix)\n {\n-\tint hit = 0;\n+\tint hit = 0, seen_dashdash = 0, use_index = 1;\n \tint cached = 0, untracked = 0, opt_exclude = -1;\n-\tint seen_dashdash = 0;\n \tint external_grep_allowed__ignored;\n+\tint i, dummy, allow_revs;\n \tconst char *show_in_pager = NULL, *default_pager = \"dummy\";\n \tstruct grep_opt opt;\n \tstruct object_array list = OBJECT_ARRAY_INIT;\n \tstruct pathspec pathspec;\n \tstruct string_list path_list = STRING_LIST_INIT_DUP;\n-\tint i;\n-\tint dummy;\n-\tint use_index = 1;\n-\tint allow_revs;\n \n \tstruct option options[] = {\n \t\tOPT_BOOL(0, \"cached\", &cached,\n@@ -1059,9 +1055,8 @@ int cmd_grep(int argc, const char **argv, const char *prefix)\n \t\trecurse_submodules = 0;\n \n \t/*\n-\t * skip a -- separator; we know it cannot be\n-\t * separating revisions from pathnames if\n-\t * we haven't even had any patterns yet\n+\t * skip a -- separator; we know it cannot be separating revisions\n+\t * from pathnames if we haven't even had any patterns yet\n \t */\n \tif (argc > 0 && !opt.pattern_list && !strcmp(argv[0], \"--\")) {\n \t\targv++;\n"},{"id":"491502","messageId":"cf9d3f4833f121b271fd8aacf4c0e2e4a9920585.1711398665.git.dsimic@manjaro.org","threadId":"61200","inReplyTo":"cover.1711398665.git.dsimic@manjaro.org","subject":"[PATCH v3 2/3] grep docs: describe --recurse-submodules further and improve formatting a bit","fromName":"Dragan Simic","fromEmail":"dsimic@manjaro.org","sentAt":"2024-03-25T20:34:52Z","receivedAt":"2024-03-25T20:34:58Z","isPatch":true,"sender":{"key":"dsimic@manjaro.org","avatar":null},"body":"Clarify that --recurse-submodules cannot be used together with --untracked,\nand improve the formatting in a couple of places, to make it visually clear\nthat those are the commands or the names of configuration options.\n\nWhile there, change a couple of \"\" placeholders to \"__\", to help\nwith an ongoing translation improvement effort. [1]\n\n[1] https://lore.kernel.org/git/CAPig+cQc8W4JOpB+TMP=czketU1U7wcY_x9bsP5T=3-XjGLhRQ@mail.gmail.com/\n\nSigned-off-by: Dragan Simic \n---\n\nNotes:\n Changes in v3:\n - No changes were introduced\n \n Changes in v2:\n - No changes were introduced\n \n This patch is salvaged from my earlier series, [2] for which it has been\n concluded to be not acceptable for merging, because of possible issues\n with various git scripts. [3]\n \n Compared to the version in the earlier series, this version adds some more\n small formatting improvements of the same kind, and also changes a couple\n of \"\" placeholders to \"__\", as suggested by Eric Sunshine. [1]\n \n [2] https://lore.kernel.org/git/cover.1710781235.git.dsimic@manjaro.org/T/#u\n [3] https://lore.kernel.org/git/d8475579f014a90b27efaf6207bc6fb0@manjaro.org/\n\n Documentation/config/grep.txt | 2 +-\n Documentation/git-grep.txt | 10 +++++-----\n 2 files changed, 6 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/config/grep.txt b/Documentation/config/grep.txt\nindex e521f20390ce..10041f27b0c8 100644\n--- a/Documentation/config/grep.txt\n+++ b/Documentation/config/grep.txt\n@@ -24,5 +24,5 @@ grep.fullName::\n \tIf set to true, enable `--full-name` option by default.\n \n grep.fallbackToNoIndex::\n-\tIf set to true, fall back to git grep --no-index if git grep\n+\tIf set to true, fall back to `git grep --no-index` if `git grep`\n \tis executed outside of a git repository. Defaults to false.\ndiff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt\nindex 0d0103c780af..f64f40e9775a 100644\n--- a/Documentation/git-grep.txt\n+++ b/Documentation/git-grep.txt\n@@ -64,9 +64,9 @@ OPTIONS\n --recurse-submodules::\n \tRecursively search in each submodule that is active and\n \tchecked out in the repository. When used in combination with the\n-\t option the prefix of all submodule output will be the name of\n-\tthe parent project's object. This option has no effect\n-\tif `--no-index` is given.\n+\t__ option the prefix of all submodule output will be the name of\n+\tthe parent project's __ object. This option cannot be used together\n+\twith `--untracked`, and it has no effect if `--no-index` is specified.\n \n -a::\n --text::\n@@ -178,7 +178,7 @@ providing this option will cause it to die.\n \tUse \\0 as the delimiter for pathnames in the output, and print\n \tthem verbatim. Without this option, pathnames with \"unusual\"\n \tcharacters are quoted as explained for the configuration\n-\tvariable core.quotePath (see linkgit:git-config[1]).\n+\tvariable `core.quotePath` (see linkgit:git-config[1]).\n \n -o::\n --only-matching::\n@@ -332,7 +332,7 @@ EXAMPLES\n NOTES ON THREADS\n ----------------\n \n-The `--threads` option (and the grep.threads configuration) will be ignored when\n+The `--threads` option (and the `grep.threads` configuration) will be ignored when\n `--open-files-in-pager` is used, forcing a single-threaded execution.\n \n When grepping the object store (with `--cached` or giving tree objects), running\n"},{"id":"491503","messageId":"41f0f16948b231316c0f23cc77747339450acb87.1711398665.git.dsimic@manjaro.org","threadId":"61200","inReplyTo":"cover.1711398665.git.dsimic@manjaro.org","subject":"[PATCH v3 3/3] grep docs: describe --no-index further and improve formatting a bit","fromName":"Dragan Simic","fromEmail":"dsimic@manjaro.org","sentAt":"2024-03-25T20:34:53Z","receivedAt":"2024-03-25T20:34:58Z","isPatch":true,"sender":{"key":"dsimic@manjaro.org","avatar":null},"body":"Improve the description of --no-index, to make it more clear to the users\nwhat this option actually does under the hood, and what's its purpose.\nDescribe the dependency between --no-index and either of the --cached and\n--untracked options, which cannot be used together.\n\nAs part of that, shuffle a couple of the options, to make the documentation\nflow a bit better, because it makes more sense to describe first the options\nthat have something in common, and to after that describe an option that does\nsomething differently. In more detail, --cached and --untracked both leave\ngit-grep(1) in the usual state, in which it treats the directory as a local\ngit repository, unlike --no-index that makes git-grep(1) treat the directory\nnot as a git repository.\n\nWhile there, improve the descriptions of grep worker threads a bit, to give\nthem better context. Adjust the language a bit, to avoid addressing the\nreader directly, which is in general preferred in technical documentation,\nbecause it eliminates the possible element of persuading the user to do\nsomething. In other words, we should be telling the user what our software\ncan do, instead of telling the user what to do.\n\nAlso perform some minor formatting improvements, to make it clear it's the\ngit commands, command parameters, and configuration option names.\n\nSigned-off-by: Dragan Simic \n---\n\nNotes:\n Changes in v3:\n - Removed references to speedups caused by multi-threaded searches,\n as pointed out by Junio, [1] because it all depends on the actual\n workloads and the actual system I/O speed and CPU power\n - One of the removed references replaced with a reference to pathspec\n patterns, which is a more suitable example of the benefits\n \n Changes in v2:\n - Improved the patch description a bit, to make it more clear why\n this patch shuffles some of the options around, and why it changes\n some of the wording to passive voice\n - Reworded the description of --no-index a bit, to not mention the\n name of the utility we're describing, which avoids any possible\n confusion, as pointed out by Jean-Noel Avila [2]\n \n This patch is salvaged from my earlier series, [3] for which it has been\n concluded to be not acceptable for merging, because of possible issues\n with various git scripts. [4]\n \n Compared to the version in the earlier series, this version continues\n the effort to improve the description of --no-index, by also incorporating\n the possible improvements pointed out by Junio. [5] This version also\n improves the wording of some related descriptions, mainly related to\n grep.threads, and performs some additional small formatting improvements.\n \n [1] https://lore.kernel.org/git/xmqqa5mmjf2f.fsf@gitster.g/\n [2] https://lore.kernel.org/git/ed050f2d496a6db07e698fd2f1094b81@manjaro.org/\n [3] https://lore.kernel.org/git/cover.1710781235.git.dsimic@manjaro.org/T/#u\n [4] https://lore.kernel.org/git/d8475579f014a90b27efaf6207bc6fb0@manjaro.org/\n [5] https://lore.kernel.org/git/xmqqwmpzrqfv.fsf@gitster.g/\n\n Documentation/git-grep.txt | 26 +++++++++++++++++---------\n 1 file changed, 17 insertions(+), 9 deletions(-)\n\ndiff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt\nindex f64f40e9775a..1e6d7b65c84e 100644\n--- a/Documentation/git-grep.txt\n+++ b/Documentation/git-grep.txt\n@@ -28,7 +28,7 @@ SYNOPSIS\n \t [-f ] [-e] \n \t [--and|--or|--not|(|)|-e ...]\n \t [--recurse-submodules] [--parent-basename ]\n-\t [ [--[no-]exclude-standard] [--cached | --no-index | --untracked] | ...]\n+\t [ [--[no-]exclude-standard] [--cached | --untracked | --no-index] | ...]\n \t [--] [...]\n \n DESCRIPTION\n@@ -45,13 +45,21 @@ OPTIONS\n \tInstead of searching tracked files in the working tree, search\n \tblobs registered in the index file.\n \n---no-index::\n-\tSearch files in the current directory that is not managed by Git.\n-\n --untracked::\n \tIn addition to searching in the tracked files in the working\n \ttree, search also in untracked files.\n \n+--no-index::\n+\tSearch files in the current directory that is not managed by Git,\n+\tor by ignoring that the current directory is managed by Git. This\n+\tis rather similar to running the regular `grep(1)` utility with its\n+\t`-r` option specified, but with some additional benefits, such as\n+\tusing pathspec patterns to limit paths; see the 'pathspec' entry\n+\tin linkgit:gitglossary[7] for more information.\n++\n+This option cannot be used together with `--cached` or `--untracked`.\n+See also `grep.fallbackToNoIndex` in 'CONFIGURATION' below.\n+\n --no-exclude-standard::\n \tAlso search in ignored files by not honoring the `.gitignore`\n \tmechanism. Only useful with `--untracked`.\n@@ -248,8 +256,8 @@ providing this option will cause it to die.\n \ta non-zero status.\n \n --threads ::\n-\tNumber of grep worker threads to use.\n-\tSee `grep.threads` in 'CONFIGURATION' for more information.\n+\tNumber of `grep` worker threads to use. See 'NOTES ON THREADS'\n+\tand `grep.threads` in 'CONFIGURATION' for more information.\n \n -f ::\n \tRead patterns from , one per line.\n@@ -336,9 +344,9 @@ The `--threads` option (and the `grep.threads` configuration) will be ignored wh\n `--open-files-in-pager` is used, forcing a single-threaded execution.\n \n When grepping the object store (with `--cached` or giving tree objects), running\n-with multiple threads might perform slower than single threaded if `--textconv`\n-is given and there are too many text conversions. So if you experience low\n-performance in this case, it might be desirable to use `--threads=1`.\n+with multiple threads might perform slower than single-threaded if `--textconv`\n+is given and there are too many text conversions. Thus, if low performance is\n+experienced in this case, it might be desirable to use `--threads=1`.\n \n CONFIGURATION\n -------------\n"},{"id":"491506","messageId":"CAPig+cTia_gXkpNw6jo8VHg=ODqX71Nvff4Qfq0oMWqShv5TWg@mail.gmail.com","threadId":"61200","inReplyTo":"cover.1711398665.git.dsimic@manjaro.org","subject":"Re: [PATCH v3 0/3] Assorted improvements salvaged from an earlier series","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2024-03-25T20:39:16Z","receivedAt":"2024-03-25T20:39:28Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Mon, Mar 25, 2024 at 4:34 PM Dragan Simic wrote:\n> This series contains patches salvaged from my earlier series, [1] for\n> which it has been concluded to be not acceptable for merging, because of\n> possible issues with various git scripts. [2]\n>\n> Changes introduced to the patches are described separately in each patch.\n\nProse description of the changes between versions is very much welcome\nby reviewers, but please also include a range-diff[1] or interdiff[2]\nwhen preparing a reroll.\n\n[1]: git format-patch --range-diff= ...\n[2]: git format-patch --interdiff= ...\n"},{"id":"491507","messageId":"92cb6c057591c7192fd7eb7097336f66@manjaro.org","threadId":"61200","inReplyTo":"CAPig+cTia_gXkpNw6jo8VHg=ODqX71Nvff4Qfq0oMWqShv5TWg@mail.gmail.com","subject":"Re: [PATCH v3 0/3] Assorted improvements salvaged from an earlier series","fromName":"Dragan Simic","fromEmail":"dsimic@manjaro.org","sentAt":"2024-03-25T20:41:14Z","receivedAt":"2024-03-25T20:41:15Z","isPatch":true,"sender":{"key":"dsimic@manjaro.org","avatar":null},"body":"On 2024-03-25 21:39, Eric Sunshine wrote:\n> On Mon, Mar 25, 2024 at 4:34 PM Dragan Simic \n> wrote:\n>> This series contains patches salvaged from my earlier series, [1] for\n>> which it has been concluded to be not acceptable for merging, because \n>> of\n>> possible issues with various git scripts. [2]\n>> \n>> Changes introduced to the patches are described separately in each \n>> patch.\n> \n> Prose description of the changes between versions is very much welcome\n> by reviewers, but please also include a range-diff[1] or interdiff[2]\n> when preparing a reroll.\n> \n> [1]: git format-patch --range-diff= ...\n> [2]: git format-patch --interdiff= ...\n\nAh, sorry, I didn't forget about that, but I just intended to start\nproviding range-diffs for future patches. These were more like new\nversions of old patches.\n"},{"id":"491510","messageId":"CAPig+cRECapN-9_u0JoESaS7KTi-==ri7Oy+sjff-VHL7p+vHQ@mail.gmail.com","threadId":"61200","inReplyTo":"92cb6c057591c7192fd7eb7097336f66@manjaro.org","subject":"Re: [PATCH v3 0/3] Assorted improvements salvaged from an earlier series","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2024-03-25T20:49:43Z","receivedAt":"2024-03-25T20:49:55Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Mon, Mar 25, 2024 at 4:41 PM Dragan Simic wrote:\n> On 2024-03-25 21:39, Eric Sunshine wrote:\n> > Prose description of the changes between versions is very much welcome\n> > by reviewers, but please also include a range-diff[1] or interdiff[2]\n> > when preparing a reroll.\n>\n> Ah, sorry, I didn't forget about that, but I just intended to start\n> providing range-diffs for future patches. These were more like new\n> versions of old patches.\n\nThe range-diff is particularly valuable exactly for this case (new\nversions of old patches) since it is a \"diff\" between the old patches\nand the new patches. Thus, it provides reviewers with a precise\nsummary of what changed between, say, v2 and v3 of a series, and\nmanifests as a concrete representation of what your prose explanation\ndescribes.\n"},{"id":"491514","messageId":"a3bc4829036f5803da513fee52267c2c@manjaro.org","threadId":"61200","inReplyTo":"CAPig+cRECapN-9_u0JoESaS7KTi-==ri7Oy+sjff-VHL7p+vHQ@mail.gmail.com","subject":"Re: [PATCH v3 0/3] Assorted improvements salvaged from an earlier series","fromName":"Dragan Simic","fromEmail":"dsimic@manjaro.org","sentAt":"2024-03-25T20:54:18Z","receivedAt":"2024-03-25T20:54:20Z","isPatch":true,"sender":{"key":"dsimic@manjaro.org","avatar":null},"body":"On 2024-03-25 21:49, Eric Sunshine wrote:\n> On Mon, Mar 25, 2024 at 4:41 PM Dragan Simic \n> wrote:\n>> On 2024-03-25 21:39, Eric Sunshine wrote:\n>> > Prose description of the changes between versions is very much welcome\n>> > by reviewers, but please also include a range-diff[1] or interdiff[2]\n>> > when preparing a reroll.\n>> \n>> Ah, sorry, I didn't forget about that, but I just intended to start\n>> providing range-diffs for future patches. These were more like new\n>> versions of old patches.\n> \n> The range-diff is particularly valuable exactly for this case (new\n> versions of old patches) since it is a \"diff\" between the old patches\n> and the new patches. Thus, it provides reviewers with a precise\n> summary of what changed between, say, v2 and v3 of a series, and\n> manifests as a concrete representation of what your prose explanation\n> describes.\n\nI see, and I do understand the purpose of range-diffs: they make\nreviewing new patch versions significantly easier, by relieving the\nreviewers from the need to track down what has been changed in the\ncurrent patch version.\n"},{"id":"492342","messageId":"f5c2c3af9813d56adf85393f0e8fde0e@manjaro.org","threadId":"61200","inReplyTo":"a3bc4829036f5803da513fee52267c2c@manjaro.org","subject":"Re: [PATCH v3 0/3] Assorted improvements salvaged from an earlier series","fromName":"Dragan Simic","fromEmail":"dsimic@manjaro.org","sentAt":"2024-04-06T00:52:16Z","receivedAt":"2024-04-06T00:52:18Z","isPatch":true,"sender":{"key":"dsimic@manjaro.org","avatar":null},"body":"Hello Eric,\n\nOn 2024-03-25 21:54, Dragan Simic wrote:\n> On 2024-03-25 21:49, Eric Sunshine wrote:\n>> On Mon, Mar 25, 2024 at 4:41 PM Dragan Simic \n>> wrote:\n>>> On 2024-03-25 21:39, Eric Sunshine wrote:\n>>> > Prose description of the changes between versions is very much welcome\n>>> > by reviewers, but please also include a range-diff[1] or interdiff[2]\n>>> > when preparing a reroll.\n>>> \n>>> Ah, sorry, I didn't forget about that, but I just intended to start\n>>> providing range-diffs for future patches. These were more like new\n>>> versions of old patches.\n>> \n>> The range-diff is particularly valuable exactly for this case (new\n>> versions of old patches) since it is a \"diff\" between the old patches\n>> and the new patches. Thus, it provides reviewers with a precise\n>> summary of what changed between, say, v2 and v3 of a series, and\n>> manifests as a concrete representation of what your prose explanation\n>> describes.\n> \n> I see, and I do understand the purpose of range-diffs: they make\n> reviewing new patch versions significantly easier, by relieving the\n> reviewers from the need to track down what has been changed in the\n> current patch version.\n\nAs a note, I kept my promise :) and have started providing range-diffs\nin patch submissions. [1]\n\n[1] \nhttps://lore.kernel.org/git/e3212c0a4ad331685c68c13afcdbced20982ab32.1712364420.git.dsimic@manjaro.org/T/#u\n"},{"id":"492361","messageId":"CAPig+cToJgRn-ao9c9wXf7g99_TL3aRfwEasA9U3e4qNC3cVMg@mail.gmail.com","threadId":"61200","inReplyTo":"f5c2c3af9813d56adf85393f0e8fde0e@manjaro.org","subject":"Re: [PATCH v3 0/3] Assorted improvements salvaged from an earlier series","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2024-04-06T01:49:00Z","receivedAt":"2024-04-06T01:49:12Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Fri, Apr 5, 2024 at 8:52 PM Dragan Simic wrote:\n> On 2024-03-25 21:54, Dragan Simic wrote:\n> > On 2024-03-25 21:49, Eric Sunshine wrote:\n> >> The range-diff is particularly valuable exactly for this case (new\n> >> versions of old patches) since it is a \"diff\" between the old patches\n> >> and the new patches. Thus, it provides reviewers with a precise\n> >> summary of what changed between, say, v2 and v3 of a series, and\n> >> manifests as a concrete representation of what your prose explanation\n> >> describes.\n> >\n> > I see, and I do understand the purpose of range-diffs: they make\n> > reviewing new patch versions significantly easier, by relieving the\n> > reviewers from the need to track down what has been changed in the\n> > current patch version.\n>\n> As a note, I kept my promise :) and have started providing range-diffs\n> in patch submissions. [1]\n\nGlad to hear. Thanks.\n"}]}