{"thread":{"id":"58505","subject":"[PATCH] doc/cat-file: allow --use-mailmap for --batch options","startedAt":"2022-09-23T19:36:05Z","lastAt":"2022-11-13T21:27:17Z","messageCount":13,"participants":["Siddharth Asthana","Christian Couder","John Cai","Junio C Hamano","Taylor Blau"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"463546","messageId":"20220923193543.58635-1-siddharthasthana31@gmail.com","threadId":"58505","inReplyTo":null,"subject":"[PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Siddharth Asthana","fromEmail":"siddharthasthana31@gmail.com","sentAt":"2022-09-23T19:35:43Z","receivedAt":"2022-09-23T19:36:05Z","isPatch":true,"sender":{"key":"siddharthasthana31@gmail.com","avatar":"https://avatars.githubusercontent.com/u/53316982?v=4"},"body":"The command git cat-file can now use the mailmap mechanism to replace\nidents with their canonical versions for commit and tag objects. There\nare several options like `--batch`, `--batch-check` and\n`--batch-command` that can be combined with `--use-mailmap`. But, the\ndocumentation for `--batch`, `--batch-check` and `--batch-command`\ndoesn't say so. This patch fixes that documentation.\n\nMentored-by: Christian Couder's avatarChristian Couder \nMentored-by: John Cai's avatarJohn Cai \nSigned-off-by: Siddharth Asthana \n---\n Documentation/git-cat-file.txt | 44 ++++++++++++++++++++++++----------\n 1 file changed, 31 insertions(+), 13 deletions(-)\n\ndiff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\nindex ec30b5c574..3fdafc07ce 100644\n--- a/Documentation/git-cat-file.txt\n+++ b/Documentation/git-cat-file.txt\n@@ -89,26 +89,44 @@ OPTIONS\n --batch::\n --batch=::\n \tPrint object information and contents for each object provided\n-\ton stdin. May not be combined with any other options or arguments\n-\texcept `--textconv` or `--filters`, in which case the input lines\n-\talso need to specify the path, separated by whitespace. See the\n-\tsection `BATCH OUTPUT` below for details.\n+\ton stdin.\n+\n+\t* When used with `--textconv` or `--filters`, the input lines\n+\t must specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t the object, if the idents recorded in it were the ones \"corrected\"\n+\t by the mailmap mechanism.\n+\t Cannot be used with any other options.\n \n --batch-check::\n --batch-check=::\n-\tPrint object information for each object provided on stdin. May\n-\tnot be combined with any other options or arguments except\n-\t`--textconv` or `--filters`, in which case the input lines also\n-\tneed to specify the path, separated by whitespace. See the\n-\tsection `BATCH OUTPUT` below for details.\n+\tPrint object information for each object provided on stdin.\n+\n+\t* When used with `--textconv` or `--filters`, the input lines must\n+\t specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t the object, if the idents recorded in it were the ones \"corrected\"\n+\t by the mailmap mechanism.\n+\t Cannot be used with any other options.\n \n --batch-command::\n --batch-command=::\n \tEnter a command mode that reads commands and arguments from stdin. May\n-\tonly be combined with `--buffer`, `--textconv` or `--filters`. In the\n-\tcase of `--textconv` or `--filters`, the input lines also need to specify\n-\tthe path, separated by whitespace. See the section `BATCH OUTPUT` below\n-\tfor details.\n+\tonly be combined with `--buffer`, `--textconv`, `--use-mailmap` or\n+\t`--filters`.\n+\n+\t* When used with `--textconv` or `--filters`, the input lines must\n+\t specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\n+\t* When used with `--use-mailmap`, the info command shows the size the\n+\t object, if the idents recorded in it were the ones \"corrected\" by the\n+\t mailmap mechanism.\n+\n +\n `--batch-command` recognizes the following commands:\n +\n-- \n2.38.0.rc1.3.g2cb248e00d.dirty\n\n"},{"id":"463571","messageId":"CAP8UFD245ebv95f8bvN9YqPtv1c+Pa4xzAmY_mixs3nrdSdGvA@mail.gmail.com","threadId":"58505","inReplyTo":"20220923193543.58635-1-siddharthasthana31@gmail.com","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-09-24T14:49:59Z","receivedAt":"2022-09-24T14:50:15Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Fri, Sep 23, 2022 at 9:36 PM Siddharth Asthana\n wrote:\n>\n> The command git cat-file can now use the mailmap mechanism to replace\n> idents with their canonical versions for commit and tag objects. There\n> are several options like `--batch`, `--batch-check` and\n> `--batch-command` that can be combined with `--use-mailmap`. But, the\n> documentation for `--batch`, `--batch-check` and `--batch-command`\n> doesn't say so. This patch fixes that documentation.\n>\n> Mentored-by: Christian Couder's avatarChristian Couder \n> Mentored-by: John Cai's avatarJohn Cai \n\nAs you told me separately, you should remove \"Christian Couder's\navatar\" and \"John Cai's avatar\" from the above trailers.\n\n> Signed-off-by: Siddharth Asthana \n> ---\n\nHere after the line that contains only '---' and before the short\nstats below, you could write some small explanations about where this\npatch comes from.\n\nFor example you could say that it was previously sent as the first\npatch of a a 3 patch series:\n\nhttps://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n\nAnd you could tell what changes you made compared to the previous patch.\n\n> Documentation/git-cat-file.txt | 44 ++++++++++++++++++++++++----------\n> 1 file changed, 31 insertions(+), 13 deletions(-)\n>\n> diff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\n> index ec30b5c574..3fdafc07ce 100644\n> --- a/Documentation/git-cat-file.txt\n> +++ b/Documentation/git-cat-file.txt\n> @@ -89,26 +89,44 @@ OPTIONS\n> --batch::\n> --batch=::\n> Print object information and contents for each object provided\n> - on stdin. May not be combined with any other options or arguments\n> - except `--textconv` or `--filters`, in which case the input lines\n> - also need to specify the path, separated by whitespace. See the\n> - section `BATCH OUTPUT` below for details.\n> + on stdin.\n> +\n> + * When used with `--textconv` or `--filters`, the input lines\n> + must specify the path, separated by whitespace. See the section\n> + `BATCH OUTPUT` below for details.\n> +\n> + * When used with `--use-mailmap`, the info command shows the size\n> + the object, if the idents recorded in it were the ones \"corrected\"\n> + by the mailmap mechanism.\n> + Cannot be used with any other options.\n\nHave you checked the result of `git help cat-file` after `make instll-doc`?\n\nShouldn't you use something like the following instead for additional\nparagraphs inside some indented text:\n\n+\n* When used with `--textconv` or `--filters`, the input lines\nmust specify the path, separated by whitespace. See the section\n`BATCH OUTPUT` below for details.\n+\n\n?\n\n(Note that the + signs in what I suggest above should be actually\nadded to the file and aren't what a diff displays in front of new\nlines.)\n\nAlso it's not very clear if \"Cannot be used with any other options.\"\nis part of the last \"* When ...\" paragraph or not.\n"},{"id":"463614","messageId":"20220926091442.222876-1-siddharthasthana31@gmail.com","threadId":"58505","inReplyTo":"20220923193543.58635-1-siddharthasthana31@gmail.com","subject":"[PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Siddharth Asthana","fromEmail":"siddharthasthana31@gmail.com","sentAt":"2022-09-26T09:14:42Z","receivedAt":"2022-09-26T09:16:16Z","isPatch":true,"sender":{"key":"siddharthasthana31@gmail.com","avatar":"https://avatars.githubusercontent.com/u/53316982?v=4"},"body":"The command git cat-file can now use the mailmap mechanism to replace\nidents with their canonical versions for commit and tag objects. There\nare several options like `--batch`, `--batch-check` and\n`--batch-command` that can be combined with `--use-mailmap`. But, the\ndocumentation for `--batch`, `--batch-check` and `--batch-command`\ndoesn't say so. This patch fixes that documentation.\n\nMentored-by: Christian Couder \nMentored-by: John Cai \nSigned-off-by: Siddharth Asthana \n---\n\nThis patch was previously sent as the first patch of a 3 patch series for \nadding the mailmap support in git cat-file options:\nhttps://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n\nChanges in v2:\n- Fixed the names in trailers in the commit message\n- Updated the documentation to clearly state that the `--batch-check`,\n `--batch-command` and `--batch` options can only be used with\n `--textconv`, `--filters` or `--use-mailmap`.\n- Fixed formating\n\n Documentation/git-cat-file.txt | 45 ++++++++++++++++++++++++----------\n 1 file changed, 32 insertions(+), 13 deletions(-)\n\ndiff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\nindex ec30b5c574..2a8f050a29 100644\n--- a/Documentation/git-cat-file.txt\n+++ b/Documentation/git-cat-file.txt\n@@ -89,26 +89,45 @@ OPTIONS\n --batch::\n --batch=::\n \tPrint object information and contents for each object provided\n-\ton stdin. May not be combined with any other options or arguments\n-\texcept `--textconv` or `--filters`, in which case the input lines\n-\talso need to specify the path, separated by whitespace. See the\n-\tsection `BATCH OUTPUT` below for details.\n+\ton stdin. May not be combined with any other options or arguments\n+\texcept --textconv, --filters or --use-mailmap.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines\n+\t must specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t the object, if the idents recorded in it were the ones \"corrected\"\n+\t by the mailmap mechanism.\n \n --batch-check::\n --batch-check=::\n-\tPrint object information for each object provided on stdin. May\n-\tnot be combined with any other options or arguments except\n-\t`--textconv` or `--filters`, in which case the input lines also\n-\tneed to specify the path, separated by whitespace. See the\n-\tsection `BATCH OUTPUT` below for details.\n+\tPrint object information for each object provided on stdin. May not be\n+\tcombined with any other options or arguments except --textconv, --filters\n+\tor --use-mailmap.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines must\n+\t specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t the object, if the idents recorded in it were the ones \"corrected\"\n+\t by the mailmap mechanism.\n \n --batch-command::\n --batch-command=::\n \tEnter a command mode that reads commands and arguments from stdin. May\n-\tonly be combined with `--buffer`, `--textconv` or `--filters`. In the\n-\tcase of `--textconv` or `--filters`, the input lines also need to specify\n-\tthe path, separated by whitespace. See the section `BATCH OUTPUT` below\n-\tfor details.\n+\tonly be combined with `--buffer`, `--textconv`, `--use-mailmap` or\n+\t`--filters`.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines must\n+\t specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size the\n+\t object, if the idents recorded in it were the ones \"corrected\" by the\n+\t mailmap mechanism.\n+\n +\n `--batch-command` recognizes the following commands:\n +\n-- \n2.38.0.rc1.4.g29ac4cf309.dirty\n\n"},{"id":"463631","messageId":"750BA887-BECB-471D-8BB2-0B321778F376@gmail.com","threadId":"58505","inReplyTo":"20220926091442.222876-1-siddharthasthana31@gmail.com","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"John Cai","fromEmail":"johncai86@gmail.com","sentAt":"2022-09-26T14:11:45Z","receivedAt":"2022-09-26T15:31:07Z","isPatch":true,"sender":{"key":"johncai86@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2354211?v=4"},"body":"Hi Siddarth,\n\nOn 26 Sep 2022, at 5:14, Siddharth Asthana wrote:\n\n> The command git cat-file can now use the mailmap mechanism to replace\n> idents with their canonical versions for commit and tag objects. There\n> are several options like `--batch`, `--batch-check` and\n> `--batch-command` that can be combined with `--use-mailmap`. But, the\n> documentation for `--batch`, `--batch-check` and `--batch-command`\n> doesn't say so. This patch fixes that documentation.\n>\n> Mentored-by: Christian Couder \n> Mentored-by: John Cai \n> Signed-off-by: Siddharth Asthana \n> ---\n>\n> This patch was previously sent as the first patch of a 3 patch series for\n> adding the mailmap support in git cat-file options:\n> https://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n>\n> Changes in v2:\n> - Fixed the names in trailers in the commit message\n> - Updated the documentation to clearly state that the `--batch-check`,\n> `--batch-command` and `--batch` options can only be used with\n> `--textconv`, `--filters` or `--use-mailmap`.\n> - Fixed formating\n>\n> Documentation/git-cat-file.txt | 45 ++++++++++++++++++++++++----------\n> 1 file changed, 32 insertions(+), 13 deletions(-)\n>\n> diff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\n> index ec30b5c574..2a8f050a29 100644\n> --- a/Documentation/git-cat-file.txt\n> +++ b/Documentation/git-cat-file.txt\n> @@ -89,26 +89,45 @@ OPTIONS\n> --batch::\n> --batch=::\n> \tPrint object information and contents for each object provided\n> -\ton stdin. May not be combined with any other options or arguments\n> -\texcept `--textconv` or `--filters`, in which case the input lines\n> -\talso need to specify the path, separated by whitespace. See the\n> -\tsection `BATCH OUTPUT` below for details.\n> +\ton stdin. May not be combined with any other options or arguments\n> +\texcept --textconv, --filters or --use-mailmap.\n\nexcept --textconv, --filters, or --use-mailmap.\n\n> +\t+\n> +\t* When used with `--textconv` or `--filters`, the input lines\n> +\t must specify the path, separated by whitespace. See the section\n> +\t `BATCH OUTPUT` below for details.\n> +\t+\n> +\t* When used with `--use-mailmap`, the info command shows the size\n> +\t the object, if the idents recorded in it were the ones \"corrected\"\n> +\t by the mailmap mechanism.\n\nWhen used with `--use-mailmap`, the info command shows the size\nthe object if the identities recorded in it were replaced\nby the mailmap mechanism.\n\n>\n> --batch-check::\n> --batch-check=::\n> -\tPrint object information for each object provided on stdin. May\n> -\tnot be combined with any other options or arguments except\n> -\t`--textconv` or `--filters`, in which case the input lines also\n> -\tneed to specify the path, separated by whitespace. See the\n> -\tsection `BATCH OUTPUT` below for details.\n> +\tPrint object information for each object provided on stdin. May not be\n> +\tcombined with any other options or arguments except --textconv, --filters\n> +\tor --use-mailmap.\n> +\t+\n> +\t* When used with `--textconv` or `--filters`, the input lines must\n> +\t specify the path, separated by whitespace. See the section\n> +\t `BATCH OUTPUT` below for details.\n> +\t+\n> +\t* When used with `--use-mailmap`, the info command shows the size\n> +\t the object, if the idents recorded in it were the ones \"corrected\"\n> +\t by the mailmap mechanism.\n\nSame as above\n\n> --batch-command::\n> --batch-command=::\n> \tEnter a command mode that reads commands and arguments from stdin. May\n> -\tonly be combined with `--buffer`, `--textconv` or `--filters`. In the\n> -\tcase of `--textconv` or `--filters`, the input lines also need to specify\n> -\tthe path, separated by whitespace. See the section `BATCH OUTPUT` below\n> -\tfor details.\n> +\tonly be combined with `--buffer`, `--textconv`, `--use-mailmap` or\n> +\t`--filters`.\n> +\t+\n> +\t* When used with `--textconv` or `--filters`, the input lines must\n> +\t specify the path, separated by whitespace. See the section\n> +\t `BATCH OUTPUT` below for details.\n> +\t+\n> +\t* When used with `--use-mailmap`, the info command shows the size the\n> +\t object, if the idents recorded in it were the ones \"corrected\" by the\n> +\t mailmap mechanism.\n\nSame as above\n\n> +\n> +\n> `--batch-command` recognizes the following commands:\n> +\n> -- \n> 2.38.0.rc1.4.g29ac4cf309.dirty\n\nthanks!\n"},{"id":"465456","messageId":"ad579a6c-8a3b-c226-54e4-b8bcef4930ac@gmail.com","threadId":"58505","inReplyTo":"750BA887-BECB-471D-8BB2-0B321778F376@gmail.com","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Siddharth Asthana","fromEmail":"siddharthasthana31@gmail.com","sentAt":"2022-10-21T10:32:53Z","receivedAt":"2022-10-21T10:33:04Z","isPatch":true,"sender":{"key":"siddharthasthana31@gmail.com","avatar":"https://avatars.githubusercontent.com/u/53316982?v=4"},"body":"\n\nOn 26/09/22 19:41, John Cai wrote:\n> Hi Siddarth,\n> \n> On 26 Sep 2022, at 5:14, Siddharth Asthana wrote:\n> \n>> The command git cat-file can now use the mailmap mechanism to replace\n>> idents with their canonical versions for commit and tag objects. There\n>> are several options like `--batch`, `--batch-check` and\n>> `--batch-command` that can be combined with `--use-mailmap`. But, the\n>> documentation for `--batch`, `--batch-check` and `--batch-command`\n>> doesn't say so. This patch fixes that documentation.\n>>\n>> Mentored-by: Christian Couder \n>> Mentored-by: John Cai \n>> Signed-off-by: Siddharth Asthana \n>> ---\n>>\n>> This patch was previously sent as the first patch of a 3 patch series for\n>> adding the mailmap support in git cat-file options:\n>> https://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n>>\n>> Changes in v2:\n>> - Fixed the names in trailers in the commit message\n>> - Updated the documentation to clearly state that the `--batch-check`,\n>> `--batch-command` and `--batch` options can only be used with\n>> `--textconv`, `--filters` or `--use-mailmap`.\n>> - Fixed formating\n>>\n>> Documentation/git-cat-file.txt | 45 ++++++++++++++++++++++++----------\n>> 1 file changed, 32 insertions(+), 13 deletions(-)\n>>\n>> diff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\n>> index ec30b5c574..2a8f050a29 100644\n>> --- a/Documentation/git-cat-file.txt\n>> +++ b/Documentation/git-cat-file.txt\n>> @@ -89,26 +89,45 @@ OPTIONS\n>> --batch::\n>> --batch=::\n>> \tPrint object information and contents for each object provided\n>> -\ton stdin. May not be combined with any other options or arguments\n>> -\texcept `--textconv` or `--filters`, in which case the input lines\n>> -\talso need to specify the path, separated by whitespace. See the\n>> -\tsection `BATCH OUTPUT` below for details.\n>> +\ton stdin. May not be combined with any other options or arguments\n>> +\texcept --textconv, --filters or --use-mailmap.\n> \n> except --textconv, --filters, or --use-mailmap.\n> \n>> +\t+\n>> +\t* When used with `--textconv` or `--filters`, the input lines\n>> +\t must specify the path, separated by whitespace. See the section\n>> +\t `BATCH OUTPUT` below for details.\n>> +\t+\n>> +\t* When used with `--use-mailmap`, the info command shows the size\n>> +\t the object, if the idents recorded in it were the ones \"corrected\"\n>> +\t by the mailmap mechanism.\n> \n> When used with `--use-mailmap`, the info command shows the size\n> the object if the identities recorded in it were replaced\n> by the mailmap mechanism.\n> \n>>\n>> --batch-check::\n>> --batch-check=::\n>> -\tPrint object information for each object provided on stdin. May\n>> -\tnot be combined with any other options or arguments except\n>> -\t`--textconv` or `--filters`, in which case the input lines also\n>> -\tneed to specify the path, separated by whitespace. See the\n>> -\tsection `BATCH OUTPUT` below for details.\n>> +\tPrint object information for each object provided on stdin. May not be\n>> +\tcombined with any other options or arguments except --textconv, --filters\n>> +\tor --use-mailmap.\n>> +\t+\n>> +\t* When used with `--textconv` or `--filters`, the input lines must\n>> +\t specify the path, separated by whitespace. See the section\n>> +\t `BATCH OUTPUT` below for details.\n>> +\t+\n>> +\t* When used with `--use-mailmap`, the info command shows the size\n>> +\t the object, if the idents recorded in it were the ones \"corrected\"\n>> +\t by the mailmap mechanism.\n> \n> Same as above\n> \n>> --batch-command::\n>> --batch-command=::\n>> \tEnter a command mode that reads commands and arguments from stdin. May\n>> -\tonly be combined with `--buffer`, `--textconv` or `--filters`. In the\n>> -\tcase of `--textconv` or `--filters`, the input lines also need to specify\n>> -\tthe path, separated by whitespace. See the section `BATCH OUTPUT` below\n>> -\tfor details.\n>> +\tonly be combined with `--buffer`, `--textconv`, `--use-mailmap` or\n>> +\t`--filters`.\n>> +\t+\n>> +\t* When used with `--textconv` or `--filters`, the input lines must\n>> +\t specify the path, separated by whitespace. See the section\n>> +\t `BATCH OUTPUT` below for details.\n>> +\t+\n>> +\t* When used with `--use-mailmap`, the info command shows the size the\n>> +\t object, if the idents recorded in it were the ones \"corrected\" by the\n>> +\t mailmap mechanism.\n> \n> Same as above\n> \n>> +\n>> +\n>> `--batch-command` recognizes the following commands:\n>> +\n>> -- \n>> 2.38.0.rc1.4.g29ac4cf309.dirty\n> \n> thanks!\n\nThanks a lot for the review John! Will make the suggested changes and \nsend the v3 patch.\n"},{"id":"465457","messageId":"20221021103442.202759-1-siddharthasthana31@gmail.com","threadId":"58505","inReplyTo":"20220923193543.58635-1-siddharthasthana31@gmail.com","subject":"[PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Siddharth Asthana","fromEmail":"siddharthasthana31@gmail.com","sentAt":"2022-10-21T10:34:41Z","receivedAt":"2022-10-21T10:35:20Z","isPatch":true,"sender":{"key":"siddharthasthana31@gmail.com","avatar":"https://avatars.githubusercontent.com/u/53316982?v=4"},"body":"The command git cat-file can now use the mailmap mechanism to replace\nidents with their canonical versions for commit and tag objects. There\nare several options like `--batch`, `--batch-check` and\n`--batch-command` that can be combined with `--use-mailmap`. But, the\ndocumentation for `--batch`, `--batch-check` and `--batch-command`\ndoesn't say so. This patch fixes that documentation.\n\nMentored-by: Christian Couder \nMentored-by: John Cai \nSigned-off-by: Siddharth Asthana \n---\n\nThis patch was previously sent as the first patch of a 3 patch series for \nadding the mailmap support in git cat-file options:\nhttps://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n\nChanges in v2:\n- Fixed the names in trailers in the commit message\n- Updated the documentation to clearly state that the `--batch-check`,\n `--batch-command` and `--batch` options can only be used with\n `--textconv`, `--filters` or `--use-mailmap`.\n- Fixed formatting\n\nChanges in v3:\n- Fixed formatting\n\n Documentation/git-cat-file.txt | 45 ++++++++++++++++++++++++----------\n 1 file changed, 32 insertions(+), 13 deletions(-)\n\ndiff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\nindex ec30b5c574..e2a179770c 100644\n--- a/Documentation/git-cat-file.txt\n+++ b/Documentation/git-cat-file.txt\n@@ -89,26 +89,45 @@ OPTIONS\n --batch::\n --batch=::\n \tPrint object information and contents for each object provided\n-\ton stdin. May not be combined with any other options or arguments\n-\texcept `--textconv` or `--filters`, in which case the input lines\n-\talso need to specify the path, separated by whitespace. See the\n-\tsection `BATCH OUTPUT` below for details.\n+\ton stdin. May not be combined with any other options or arguments\n+\texcept --textconv, --filters, or --use-mailmap.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines\n+\t must specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t the object if the identities recorded in it were replaced\n+\t by the mailmap mechanism.\n \n --batch-check::\n --batch-check=::\n-\tPrint object information for each object provided on stdin. May\n-\tnot be combined with any other options or arguments except\n-\t`--textconv` or `--filters`, in which case the input lines also\n-\tneed to specify the path, separated by whitespace. See the\n-\tsection `BATCH OUTPUT` below for details.\n+\tPrint object information for each object provided on stdin. May not be\n+\tcombined with any other options or arguments except --textconv, --filters\n+\tor --use-mailmap.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines must\n+\t specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t the object if the identities recorded in it were replaced\n+\t by the mailmap mechanism.\n \n --batch-command::\n --batch-command=::\n \tEnter a command mode that reads commands and arguments from stdin. May\n-\tonly be combined with `--buffer`, `--textconv` or `--filters`. In the\n-\tcase of `--textconv` or `--filters`, the input lines also need to specify\n-\tthe path, separated by whitespace. See the section `BATCH OUTPUT` below\n-\tfor details.\n+\tonly be combined with `--buffer`, `--textconv`, `--use-mailmap` or\n+\t`--filters`.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines must\n+\t specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t the object if the identities recorded in it were replaced\n+\t by the mailmap mechanism.\n+\n +\n `--batch-command` recognizes the following commands:\n +\n-- \n2.38.0.84.g1cc2920221\n\n"},{"id":"465504","messageId":"xmqqk04tj99k.fsf@gitster.g","threadId":"58505","inReplyTo":"20221021103442.202759-1-siddharthasthana31@gmail.com","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-10-21T18:56:23Z","receivedAt":"2022-10-21T18:56:38Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Siddharth Asthana writes:\n\n> Changes in v3:\n> - Fixed formatting\n\nThis seems to format well, both with AsciiDoc and Asciidoctor.\n\n> -\ton stdin. May not be combined with any other options or arguments\n> -\texcept `--textconv` or `--filters`, in which case the input lines\n> -\talso need to specify the path, separated by whitespace. See the\n> -\tsection `BATCH OUTPUT` below for details.\n> +\ton stdin. May not be combined with any other options or arguments\n\nUnnecessary change here, but I'll let it pass this time.\n\n> +\texcept --textconv, --filters, or --use-mailmap.\n> +\t+\n> +\t* When used with `--textconv` or `--filters`, the input lines\n> +\t must specify the path, separated by whitespace. See the section\n> +\t `BATCH OUTPUT` below for details.\n\nOK.\n\n> +\t+\n> +\t* When used with `--use-mailmap`, the info command shows the size\n> +\t the object if the identities recorded in it were replaced\n> +\t by the mailmap mechanism.\n\nDid you mean \"the object as if the identities ... were replaced\"?\n\nAll three comments equally apply to the other two hunks for\n--batch-check and --batch-command.\n\nThanks.\n"},{"id":"466008","messageId":"20221029092513.73982-1-siddharthasthana31@gmail.com","threadId":"58505","inReplyTo":"20220923193543.58635-1-siddharthasthana31@gmail.com","subject":"[PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Siddharth Asthana","fromEmail":"siddharthasthana31@gmail.com","sentAt":"2022-10-29T09:25:13Z","receivedAt":"2022-10-29T09:25:30Z","isPatch":true,"sender":{"key":"siddharthasthana31@gmail.com","avatar":"https://avatars.githubusercontent.com/u/53316982?v=4"},"body":"The command git cat-file can now use the mailmap mechanism to replace\nidents with their canonical versions for commit and tag objects. There\nare several options like `--batch`, `--batch-check` and\n`--batch-command` that can be combined with `--use-mailmap`. But, the\ndocumentation for `--batch`, `--batch-check` and `--batch-command`\ndoesn't say so. This patch fixes that documentation.\n\nMentored-by: Christian Couder \nMentored-by: John Cai \nSigned-off-by: Siddharth Asthana \n---\n\nThis patch was previously sent as the first patch of a 3 patch series for \nadding the mailmap support in git cat-file options:\nhttps://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n\nChanges in v2:\n- Fixed the names in trailers in the commit message\n- Updated the documentation to clearly state that the `--batch-check`,\n `--batch-command` and `--batch` options can only be used with\n `--textconv`, `--filters` or `--use-mailmap`.\n- Fixed formatting\n\nChanges in v3:\n- Fixed formatting\n\nChanges in v4:\n- Fixed some grammatical errors\n\n Documentation/git-cat-file.txt | 45 ++++++++++++++++++++++++----------\n 1 file changed, 32 insertions(+), 13 deletions(-)\n\ndiff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\nindex ec30b5c574..db2bba9b65 100644\n--- a/Documentation/git-cat-file.txt\n+++ b/Documentation/git-cat-file.txt\n@@ -89,26 +89,45 @@ OPTIONS\n --batch::\n --batch=::\n \tPrint object information and contents for each object provided\n-\ton stdin. May not be combined with any other options or arguments\n-\texcept `--textconv` or `--filters`, in which case the input lines\n-\talso need to specify the path, separated by whitespace. See the\n-\tsection `BATCH OUTPUT` below for details.\n+\ton stdin. May not be combined with any other options or arguments\n+\texcept --textconv, --filters, or --use-mailmap.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines\n+\t must specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t of the object as if the identities recorded in it were replaced\n+\t by the mailmap mechanism.\n \n --batch-check::\n --batch-check=::\n-\tPrint object information for each object provided on stdin. May\n-\tnot be combined with any other options or arguments except\n-\t`--textconv` or `--filters`, in which case the input lines also\n-\tneed to specify the path, separated by whitespace. See the\n-\tsection `BATCH OUTPUT` below for details.\n+\tPrint object information for each object provided on stdin. May not be\n+\tcombined with any other options or arguments except --textconv, --filters\n+\tor --use-mailmap.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines must\n+\t specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t of the object as if the identities recorded in it were replaced\n+\t by the mailmap mechanism.\n \n --batch-command::\n --batch-command=::\n \tEnter a command mode that reads commands and arguments from stdin. May\n-\tonly be combined with `--buffer`, `--textconv` or `--filters`. In the\n-\tcase of `--textconv` or `--filters`, the input lines also need to specify\n-\tthe path, separated by whitespace. See the section `BATCH OUTPUT` below\n-\tfor details.\n+\tonly be combined with `--buffer`, `--textconv`, `--use-mailmap` or\n+\t`--filters`.\n+\t+\n+\t* When used with `--textconv` or `--filters`, the input lines must\n+\t specify the path, separated by whitespace. See the section\n+\t `BATCH OUTPUT` below for details.\n+\t+\n+\t* When used with `--use-mailmap`, the info command shows the size\n+\t of the object as if the identities recorded in it were replaced\n+\t by the mailmap mechanism.\n+\n +\n `--batch-command` recognizes the following commands:\n +\n-- \n2.38.1.281.g0b8e165806.dirty\n\n"},{"id":"466028","messageId":"Y11rnKwuR0q47ngq@nand.local","threadId":"58505","inReplyTo":"20221029092513.73982-1-siddharthasthana31@gmail.com","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2022-10-29T18:06:20Z","receivedAt":"2022-10-29T18:06:26Z","isPatch":true,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"Hi Siddharth,\n\nOn Sat, Oct 29, 2022 at 02:55:13PM +0530, Siddharth Asthana wrote:\n> This patch was previously sent as the first patch of a 3 patch series for\n> adding the mailmap support in git cat-file options:\n> https://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n\nWhy was this split off from the original series? I don't have a problem\nqueueing the two topics independently, but an explanation of how the two\ninteract would be appreciated.\n\nE.g., does one depend on the other? Are they independent and can be\nmerged at will? Should the integrator expect merge conflicts?\n\nThanks,\nTaylor\n"},{"id":"466042","messageId":"CAP8UFD3J3Q4UTGo5aaDDVth1hXLXAt53322z3TSNWTVRNiJ8Xg@mail.gmail.com","threadId":"58505","inReplyTo":"Y11rnKwuR0q47ngq@nand.local","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-10-30T07:06:19Z","receivedAt":"2022-10-30T07:06:34Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Taylor,\n\nOn Sat, Oct 29, 2022 at 8:06 PM Taylor Blau wrote:\n>\n> Hi Siddharth,\n>\n> On Sat, Oct 29, 2022 at 02:55:13PM +0530, Siddharth Asthana wrote:\n> > This patch was previously sent as the first patch of a 3 patch series for\n> > adding the mailmap support in git cat-file options:\n> > https://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n>\n> Why was this split off from the original series? I don't have a problem\n> queueing the two topics independently, but an explanation of how the two\n> interact would be appreciated.\n\nI think it was split off from the original series because it's a\ndocumentation fix that could hopefully have graduated faster, and\ncould perhaps have made it into v2.38.0. Or perhaps it could make it\nin v2.38.2 if such a bug fix release is made.\n\n> E.g., does one depend on the other? Are they independent and can be\n> merged at will? Should the integrator expect merge conflicts?\n\nThe other patch series has some code changes that are independent, but\nthe documentation changes it makes should probably go on top of this.\n\nThanks,\nChristian.\n"},{"id":"466062","messageId":"Y169Zbtvr33rBQvc@nand.local","threadId":"58505","inReplyTo":"CAP8UFD3J3Q4UTGo5aaDDVth1hXLXAt53322z3TSNWTVRNiJ8Xg@mail.gmail.com","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2022-10-30T18:07:33Z","receivedAt":"2022-10-30T18:07:38Z","isPatch":true,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Sun, Oct 30, 2022 at 08:06:19AM +0100, Christian Couder wrote:\n> > Why was this split off from the original series? I don't have a problem\n> > queueing the two topics independently, but an explanation of how the two\n> > interact would be appreciated.\n>\n> I think it was split off from the original series because it's a\n> documentation fix that could hopefully have graduated faster, and\n> could perhaps have made it into v2.38.0. Or perhaps it could make it\n> in v2.38.2 if such a bug fix release is made.\n\nOK. Can we please get an updated round that clearly indicates which\nversion it is? There are several messages in this thread with the same\nsubject line and it is unclear which one reviewers are happy with.\n\nThanks,\nTaylor\n"},{"id":"466080","messageId":"CAP8UFD2vLnE8Suf259RWQk2fcq+gDFTi+cDr9mrbidY49n3Lzw@mail.gmail.com","threadId":"58505","inReplyTo":"20221029092513.73982-1-siddharthasthana31@gmail.com","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2022-10-31T10:54:40Z","receivedAt":"2022-10-31T10:55:02Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Sat, Oct 29, 2022 at 11:25 AM Siddharth Asthana\n wrote:\n>\n> The command git cat-file can now use the mailmap mechanism to replace\n> idents with their canonical versions for commit and tag objects. There\n> are several options like `--batch`, `--batch-check` and\n> `--batch-command` that can be combined with `--use-mailmap`. But, the\n> documentation for `--batch`, `--batch-check` and `--batch-command`\n> doesn't say so. This patch fixes that documentation.\n>\n> Mentored-by: Christian Couder \n> Mentored-by: John Cai \n> Signed-off-by: Siddharth Asthana \n> ---\n>\n> This patch was previously sent as the first patch of a 3 patch series for\n> adding the mailmap support in git cat-file options:\n> https://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n\nI think Taylor is probably right that there should be a version number\nat the start of the subject line if the patch has already been sent\nmany times with the same subject and mostly the same content to the\nlist.\n\n> Changes in v2:\n> - Fixed the names in trailers in the commit message\n> - Updated the documentation to clearly state that the `--batch-check`,\n> `--batch-command` and `--batch` options can only be used with\n> `--textconv`, `--filters` or `--use-mailmap`.\n> - Fixed formatting\n>\n> Changes in v3:\n> - Fixed formatting\n>\n> Changes in v4:\n> - Fixed some grammatical errors\n\nThe version number should logically be \"v4\" according to the above.\n\n> Documentation/git-cat-file.txt | 45 ++++++++++++++++++++++++----------\n> 1 file changed, 32 insertions(+), 13 deletions(-)\n>\n> diff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\n> index ec30b5c574..db2bba9b65 100644\n> --- a/Documentation/git-cat-file.txt\n> +++ b/Documentation/git-cat-file.txt\n> @@ -89,26 +89,45 @@ OPTIONS\n> --batch::\n> --batch=::\n> Print object information and contents for each object provided\n> - on stdin. May not be combined with any other options or arguments\n> - except `--textconv` or `--filters`, in which case the input lines\n> - also need to specify the path, separated by whitespace. See the\n> - section `BATCH OUTPUT` below for details.\n> + on stdin. May not be combined with any other options or arguments\n> + except --textconv, --filters, or --use-mailmap.\n> + +\n> + * When used with `--textconv` or `--filters`, the input lines\n> + must specify the path, separated by whitespace. See the section\n> + `BATCH OUTPUT` below for details.\n> + +\n> + * When used with `--use-mailmap`, the info command shows the size\n> + of the object as if the identities recorded in it were replaced\n> + by the mailmap mechanism.\n\nSorry to realize this only at this point but actually I think the\n`info` command is only available when the `--batch-command` option is\nused, not when the `--batch` option is used.\n\nAs the `--batch` option prints both object information (which includes\nthe size) and contents (which includes the idents), I think something\nlike the following should be used here:\n\n * When used with `--use-mailmap`, for commit and tag objects, the\n contents part of the output shows the identities replaced using the\n mailmap mechanism, while the information part of the output shows\n the size of the object as if it actually recorded the replacement\n identities.\n\n> --batch-check::\n> --batch-check=::\n> - Print object information for each object provided on stdin. May\n> - not be combined with any other options or arguments except\n> - `--textconv` or `--filters`, in which case the input lines also\n> - need to specify the path, separated by whitespace. See the\n> - section `BATCH OUTPUT` below for details.\n> + Print object information for each object provided on stdin. May not be\n> + combined with any other options or arguments except --textconv, --filters\n> + or --use-mailmap.\n> + +\n> + * When used with `--textconv` or `--filters`, the input lines must\n> + specify the path, separated by whitespace. See the section\n> + `BATCH OUTPUT` below for details.\n> + +\n> + * When used with `--use-mailmap`, the info command shows the size\n> + of the object as if the identities recorded in it were replaced\n> + by the mailmap mechanism.\n\nSame remark about the `info` command as above.\n\nAs the `--batch-check` option prints only object information (which\nincludes the size), I think something like the following should be\nused here:\n\n * When used with `--use-mailmap`, for commit and tag objects, the\n printed object information shows the size of the object as if the\n identities recorded in it were replaced by the mailmap mechanism.\n\n> --batch-command::\n> --batch-command=::\n> Enter a command mode that reads commands and arguments from stdin. May\n> - only be combined with `--buffer`, `--textconv` or `--filters`. In the\n> - case of `--textconv` or `--filters`, the input lines also need to specify\n> - the path, separated by whitespace. See the section `BATCH OUTPUT` below\n> - for details.\n> + only be combined with `--buffer`, `--textconv`, `--use-mailmap` or\n> + `--filters`.\n> + +\n> + * When used with `--textconv` or `--filters`, the input lines must\n> + specify the path, separated by whitespace. See the section\n> + `BATCH OUTPUT` below for details.\n> + +\n> + * When used with `--use-mailmap`, the info command shows the size\n> + of the object as if the identities recorded in it were replaced\n> + by the mailmap mechanism.\n\ns/info command/`info` command/\n\nAnd I think it could be interesting to add:\n\n - that it happens only for commits and tags, and\n - that when the `contents` command is used the idents are replaced.\n\nSo maybe something like:\n\n * When used with `--use-mailmap`, for commit and tag objects, the\n `contents` command shows the identities replaced using the\n mailmap mechanism, while the `info` command shows the size\n of the object as if it actually recorded the replacement\n identities.\n\nAlso this will become true only after your other patch series will be\nmerged. Which means that you should say somewhere that either\n\n - this patch should be merged only after the other patch series is merged, or\n - it's a bug that the `info` command doesn't show the size of the\nupdated object and this is going to be fixed soon by the other patch\nseries anyway.\n\nThanks for working on finishing this!\nChristian.\n"},{"id":"467224","messageId":"a446840e-7a6d-984b-ac15-f6359a18595a@gmail.com","threadId":"58505","inReplyTo":"CAP8UFD2vLnE8Suf259RWQk2fcq+gDFTi+cDr9mrbidY49n3Lzw@mail.gmail.com","subject":"Re: [PATCH] doc/cat-file: allow --use-mailmap for --batch options","fromName":"Siddharth Asthana","fromEmail":"siddharthasthana31@gmail.com","sentAt":"2022-11-13T21:26:52Z","receivedAt":"2022-11-13T21:27:17Z","isPatch":true,"sender":{"key":"siddharthasthana31@gmail.com","avatar":"https://avatars.githubusercontent.com/u/53316982?v=4"},"body":"\n\nOn 31/10/22 16:24, Christian Couder wrote:\n> On Sat, Oct 29, 2022 at 11:25 AM Siddharth Asthana\n> wrote:\n>>\n>> The command git cat-file can now use the mailmap mechanism to replace\n>> idents with their canonical versions for commit and tag objects. There\n>> are several options like `--batch`, `--batch-check` and\n>> `--batch-command` that can be combined with `--use-mailmap`. But, the\n>> documentation for `--batch`, `--batch-check` and `--batch-command`\n>> doesn't say so. This patch fixes that documentation.\n>>\n>> Mentored-by: Christian Couder \n>> Mentored-by: John Cai \n>> Signed-off-by: Siddharth Asthana \n>> ---\n>>\n>> This patch was previously sent as the first patch of a 3 patch series for\n>> adding the mailmap support in git cat-file options:\n>> https://lore.kernel.org/git/20220916205946.178925-2-siddharthasthana31@gmail.com/\n> \n> I think Taylor is probably right that there should be a version number\n> at the start of the subject line if the patch has already been sent\n> many times with the same subject and mostly the same content to the\n> list.\n> \n>> Changes in v2:\n>> - Fixed the names in trailers in the commit message\n>> - Updated the documentation to clearly state that the `--batch-check`,\n>> `--batch-command` and `--batch` options can only be used with\n>> `--textconv`, `--filters` or `--use-mailmap`.\n>> - Fixed formatting\n>>\n>> Changes in v3:\n>> - Fixed formatting\n>>\n>> Changes in v4:\n>> - Fixed some grammatical errors\n> \n> The version number should logically be \"v4\" according to the above.\n> \n>> Documentation/git-cat-file.txt | 45 ++++++++++++++++++++++++----------\n>> 1 file changed, 32 insertions(+), 13 deletions(-)\n>>\n>> diff --git a/Documentation/git-cat-file.txt b/Documentation/git-cat-file.txt\n>> index ec30b5c574..db2bba9b65 100644\n>> --- a/Documentation/git-cat-file.txt\n>> +++ b/Documentation/git-cat-file.txt\n>> @@ -89,26 +89,45 @@ OPTIONS\n>> --batch::\n>> --batch=::\n>> Print object information and contents for each object provided\n>> - on stdin. May not be combined with any other options or arguments\n>> - except `--textconv` or `--filters`, in which case the input lines\n>> - also need to specify the path, separated by whitespace. See the\n>> - section `BATCH OUTPUT` below for details.\n>> + on stdin. May not be combined with any other options or arguments\n>> + except --textconv, --filters, or --use-mailmap.\n>> + +\n>> + * When used with `--textconv` or `--filters`, the input lines\n>> + must specify the path, separated by whitespace. See the section\n>> + `BATCH OUTPUT` below for details.\n>> + +\n>> + * When used with `--use-mailmap`, the info command shows the size\n>> + of the object as if the identities recorded in it were replaced\n>> + by the mailmap mechanism.\n> \n> Sorry to realize this only at this point but actually I think the\n> `info` command is only available when the `--batch-command` option is\n> used, not when the `--batch` option is used.\n> \n> As the `--batch` option prints both object information (which includes\n> the size) and contents (which includes the idents), I think something\n> like the following should be used here:\n> \n> * When used with `--use-mailmap`, for commit and tag objects, the\n> contents part of the output shows the identities replaced using the\n> mailmap mechanism, while the information part of the output shows\n> the size of the object as if it actually recorded the replacement\n> identities.\n> \n>> --batch-check::\n>> --batch-check=::\n>> - Print object information for each object provided on stdin. May\n>> - not be combined with any other options or arguments except\n>> - `--textconv` or `--filters`, in which case the input lines also\n>> - need to specify the path, separated by whitespace. See the\n>> - section `BATCH OUTPUT` below for details.\n>> + Print object information for each object provided on stdin. May not be\n>> + combined with any other options or arguments except --textconv, --filters\n>> + or --use-mailmap.\n>> + +\n>> + * When used with `--textconv` or `--filters`, the input lines must\n>> + specify the path, separated by whitespace. See the section\n>> + `BATCH OUTPUT` below for details.\n>> + +\n>> + * When used with `--use-mailmap`, the info command shows the size\n>> + of the object as if the identities recorded in it were replaced\n>> + by the mailmap mechanism.\n> \n> Same remark about the `info` command as above.\n> \n> As the `--batch-check` option prints only object information (which\n> includes the size), I think something like the following should be\n> used here:\n> \n> * When used with `--use-mailmap`, for commit and tag objects, the\n> printed object information shows the size of the object as if the\n> identities recorded in it were replaced by the mailmap mechanism.\n> \n>> --batch-command::\n>> --batch-command=::\n>> Enter a command mode that reads commands and arguments from stdin. May\n>> - only be combined with `--buffer`, `--textconv` or `--filters`. In the\n>> - case of `--textconv` or `--filters`, the input lines also need to specify\n>> - the path, separated by whitespace. See the section `BATCH OUTPUT` below\n>> - for details.\n>> + only be combined with `--buffer`, `--textconv`, `--use-mailmap` or\n>> + `--filters`.\n>> + +\n>> + * When used with `--textconv` or `--filters`, the input lines must\n>> + specify the path, separated by whitespace. See the section\n>> + `BATCH OUTPUT` below for details.\n>> + +\n>> + * When used with `--use-mailmap`, the info command shows the size\n>> + of the object as if the identities recorded in it were replaced\n>> + by the mailmap mechanism.\n> \n> s/info command/`info` command/\n> \n> And I think it could be interesting to add:\n> \n> - that it happens only for commits and tags, and\n> - that when the `contents` command is used the idents are replaced.\n> \n> So maybe something like:\n> \n> * When used with `--use-mailmap`, for commit and tag objects, the\n> `contents` command shows the identities replaced using the\n> mailmap mechanism, while the `info` command shows the size\n> of the object as if it actually recorded the replacement\n> identities.\n> \n> Also this will become true only after your other patch series will be\n> merged. Which means that you should say somewhere that either\n> \n> - this patch should be merged only after the other patch series is merged, or\n> - it's a bug that the `info` command doesn't show the size of the\n> updated object and this is going to be fixed soon by the other patch\n> series anyway.\n> \n> Thanks for working on finishing this!\n> Christian.\n\nThanks a ton for the review Christian :) Will make the suggested changes \nand send the v4 patch series.\n"}]}