{"thread":{"id":"57478","subject":"[PATCH] fix: include the type flag in the cli docs","startedAt":"2022-02-26T05:34:27Z","lastAt":"2022-03-04T16:16:14Z","messageCount":9,"participants":["Matheus Felipe via GitGitGadget","Bagas Sanjaya","Junio C Hamano","Ævar Arnfjörð Bjarmason","Matheus Felipe"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"449653","messageId":"pull.1220.git.git.1645853661519.gitgitgadget@gmail.com","threadId":"57478","inReplyTo":null,"subject":"[PATCH] fix: include the type flag in the cli docs","fromName":"Matheus Felipe via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2022-02-26T05:34:21Z","receivedAt":"2022-02-26T05:34:27Z","isPatch":true,"sender":{"key":"matheusfelipeog@protonmail.com","avatar":"https://avatars.githubusercontent.com/u/50463866?v=4"},"body":"From: Matheus Felipe <matheusfelipeog@protonmail.com>\n\nWhen the `git config --global --help` command is invoked,\nthe cli documentation is shown in the terminal with a small\nerror in one of the values of the Type group, which is the\nabsence of the type flag in the `--type` argument.\nThis commit fixes that.\n\nSigned-off-by: Matheus Felipe <matheusfelipeog@protonmail.com>\n---\n    fix: include the type flag in the cli docs\n    \n    When the git config --global --help command is invoked, the cli\n    documentation is shown in the terminal with a small error in one of the\n    values of the Type group, which is the absence of the type flag in the\n    --type argument:\n    \n    image\n    [https://user-images.githubusercontent.com/50463866/155674905-01fcdf18-8f67-488a-b367-985040dfe57d.png]\n    \n    In the web documentation and man page:\n    \n    image\n    [https://user-images.githubusercontent.com/50463866/155675353-4a39965a-875c-475c-829d-7849a982f5b9.png]\n    image\n    [https://user-images.githubusercontent.com/50463866/155675437-7283dbac-fff2-44b7-8733-7d5af375bce4.png]\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1220%2Fmatheusfelipeog%2Ffix%2Fgit-config-docs-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1220/matheusfelipeog/fix/git-config-docs-v1\nPull-Request: https://github.com/git/git/pull/1220\n\n builtin/config.c | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/builtin/config.c b/builtin/config.c\nindex 542d8d02b2b..2aea465466b 100644\n--- a/builtin/config.c\n+++ b/builtin/config.c\n@@ -151,7 +151,7 @@ static struct option builtin_config_options[] = {\n \tOPT_BIT(0, \"get-color\", &actions, N_(\"find the color configured: slot [default]\"), ACTION_GET_COLOR),\n \tOPT_BIT(0, \"get-colorbool\", &actions, N_(\"find the color setting: slot [stdout-is-tty]\"), ACTION_GET_COLORBOOL),\n \tOPT_GROUP(N_(\"Type\")),\n-\tOPT_CALLBACK('t', \"type\", &type, \"\", N_(\"value is given this type\"), option_parse_type),\n+\tOPT_CALLBACK('t', \"type\", &type, N_(\"type\"), N_(\"value is given this type\"), option_parse_type),\n \tOPT_CALLBACK_VALUE(0, \"bool\", &type, N_(\"value is \\\"true\\\" or \\\"false\\\"\"), TYPE_BOOL),\n \tOPT_CALLBACK_VALUE(0, \"int\", &type, N_(\"value is decimal number\"), TYPE_INT),\n \tOPT_CALLBACK_VALUE(0, \"bool-or-int\", &type, N_(\"value is --bool or --int\"), TYPE_BOOL_OR_INT),\n\nbase-commit: dab1b7905d0b295f1acef9785bb2b9cbb0fdec84\n-- \ngitgitgadget\n"},{"id":"449684","messageId":"f171e157-7dbc-b07e-7164-c62e2427fbe2@gmail.com","threadId":"57478","inReplyTo":"pull.1220.git.git.1645853661519.gitgitgadget@gmail.com","subject":"Re: [PATCH] fix: include the type flag in the cli docs","fromName":"Bagas Sanjaya","fromEmail":"bagasdotme@gmail.com","sentAt":"2022-02-27T04:29:06Z","receivedAt":"2022-02-27T04:29:33Z","isPatch":true,"sender":{"key":"bagasdotme@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40219486?v=4"},"body":"On 26/02/22 12.34, Matheus Felipe via GitGitGadget wrote:\n> From: Matheus Felipe <matheusfelipeog@protonmail.com>\n> \n> When the `git config --global --help` command is invoked,\n> the cli documentation is shown in the terminal with a small\n> error in one of the values of the Type group, which is the\n> absence of the type flag in the `--type` argument.\n> This commit fixes that.\n> \n\nWhat about the commit message below?\n\n```\nThe usage help for --type option of `git config` is missing `type`\nin the argument placeholder (`<>`). Add it.\n```\n\n> -\tOPT_CALLBACK('t', \"type\", &type, \"\", N_(\"value is given this type\"), option_parse_type),\n> +\tOPT_CALLBACK('t', \"type\", &type, N_(\"type\"), N_(\"value is given this type\"), option_parse_type),\n\n\nThe help should be `give the value the specified type`.\n\n-- \nAn old man doll... just what I always wanted! - Clara\n"},{"id":"449705","messageId":"xmqqilt03xat.fsf@gitster.g","threadId":"57478","inReplyTo":"f171e157-7dbc-b07e-7164-c62e2427fbe2@gmail.com","subject":"Re: [PATCH] fix: include the type flag in the cli docs","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-02-27T19:48:58Z","receivedAt":"2022-02-27T19:49:06Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Bagas Sanjaya <bagasdotme@gmail.com> writes:\n\n> On 26/02/22 12.34, Matheus Felipe via GitGitGadget wrote:\n>> From: Matheus Felipe <matheusfelipeog@protonmail.com>\n>> When the `git config --global --help` command is invoked,\n>> the cli documentation is shown in the terminal with a small\n>> error in one of the values of the Type group, which is the\n>> absence of the type flag in the `--type` argument.\n>> This commit fixes that.\n>> \n>\n> What about the commit message below?\n>\n> ```\n> The usage help for --type option of `git config` is missing `type`\n> in the argument placeholder (`<>`). Add it.\n> ```\n\nIt is more concise, and at the same time points out the problem\nbeing addressed a lot more explicitly.  Much better.\n\n>> -\tOPT_CALLBACK('t', \"type\", &type, \"\", N_(\"value is given this type\"), option_parse_type),\n>> +\tOPT_CALLBACK('t', \"type\", &type, N_(\"type\"), N_(\"value is given this type\"), option_parse_type),\n>\n>\n> The help should be `give the value the specified type`.\n\nI am not sure if this is much of an improvement.\n\n    $ git config --type=bool junk.flag 0\n    $ git config junk.flag\n    false\n\nuses the type information to turn \"0\" into \"false\" before it writes\nthe value set to the variable to the file, while\n\n    $ git config junk.flag 0\n    $ git config junk.flag\n    0\n    $ git config --type=bool junk.flag\n    false\n\nshows that a stored value of \"0\" can be turned into \"false\" when\nshowing.  \"Give the value the specified type\" does not capture the\nessense in either direction.\n\n    Before setting or showing, convert the value to its canonical\n    representation according to the given type.\n\nis what we want to convey, but it is quote a mouthful as-is.\n\nSaying \"Assume the value is of this type\" would strongly imply\n\"Convert ... to its canonical reporesentation\", and the current\n\"value is given this type\" may be a close enough and shorter\napproximation of it.  I dunno.\n\n"},{"id":"449815","messageId":"220228.86a6ea38z9.gmgdl@evledraar.gmail.com","threadId":"57478","inReplyTo":"xmqqilt03xat.fsf@gitster.g","subject":"Re: [PATCH] fix: include the type flag in the cli docs","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2022-02-28T22:42:21Z","receivedAt":"2022-02-28T22:46:39Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Sun, Feb 27 2022, Junio C Hamano wrote:\n\n> Bagas Sanjaya <bagasdotme@gmail.com> writes:\n>\n>> On 26/02/22 12.34, Matheus Felipe via GitGitGadget wrote:\n>>> From: Matheus Felipe <matheusfelipeog@protonmail.com>\n>>> When the `git config --global --help` command is invoked,\n>>> the cli documentation is shown in the terminal with a small\n>>> error in one of the values of the Type group, which is the\n>>> absence of the type flag in the `--type` argument.\n>>> This commit fixes that.\n>>> \n>>\n>> What about the commit message below?\n>>\n>> ```\n>> The usage help for --type option of `git config` is missing `type`\n>> in the argument placeholder (`<>`). Add it.\n>> ```\n>\n> It is more concise, and at the same time points out the problem\n> being addressed a lot more explicitly.  Much better.\n>\n>>> -\tOPT_CALLBACK('t', \"type\", &type, \"\", N_(\"value is given this type\"), option_parse_type),\n>>> +\tOPT_CALLBACK('t', \"type\", &type, N_(\"type\"), N_(\"value is given this type\"), option_parse_type),\n>>\n>>\n>> The help should be `give the value the specified type`.\n>\n> I am not sure if this is much of an improvement.\n>\n>     $ git config --type=bool junk.flag 0\n>     $ git config junk.flag\n>     false\n>\n> uses the type information to turn \"0\" into \"false\" before it writes\n> the value set to the variable to the file, while\n>\n>     $ git config junk.flag 0\n>     $ git config junk.flag\n>     0\n>     $ git config --type=bool junk.flag\n>     false\n>\n> shows that a stored value of \"0\" can be turned into \"false\" when\n> showing.  \"Give the value the specified type\" does not capture the\n> essense in either direction.\n>\n>     Before setting or showing, convert the value to its canonical\n>     representation according to the given type.\n>\n> is what we want to convey, but it is quote a mouthful as-is.\n>\n> Saying \"Assume the value is of this type\" would strongly imply\n> \"Convert ... to its canonical reporesentation\", and the current\n> \"value is given this type\" may be a close enough and shorter\n> approximation of it.  I dunno.\n\nPerhaps:\n\n\t\"coerce (on read and write) <value> to <type>\"\n\nor:\n\n\t\"coerce (on read & write) <value> to <type>\"\n\nor:\n\n\t\"coerce (on rw) <value> to <type>\"\n\nFor the short help, depending on how verbose we'd like to be?\n\nIn any case a follow-up fix, just the \"\" to \"type\" being proposed here\nis orthagonal & looks good to me.\n\n"},{"id":"450352","messageId":"Uywg4gVveJ2mBefUUQDfm4i2U4gv2dk_MDNu1GhqklSMya5McKJ7n8enKWDFq_mWrfWlSDlxwSVBNwEAuq27osjfDNJziIy0EIE0nsVmsqM=@protonmail.com","threadId":"57478","inReplyTo":"220228.86a6ea38z9.gmgdl@evledraar.gmail.com","subject":"Re: [PATCH] fix: include the type flag in the cli docs","fromName":"Matheus Felipe","fromEmail":"matheusfelipeog@protonmail.com","sentAt":"2022-03-04T03:56:40Z","receivedAt":"2022-03-04T03:56:52Z","isPatch":true,"sender":{"key":"matheusfelipeog@protonmail.com","avatar":"https://avatars.githubusercontent.com/u/50463866?v=4"},"body":"> On 26/02/22 12.34, Matheus Felipe via GitGitGadget wrote:\n>\n> > From: Matheus Felipe matheusfelipeog@protonmail.com\n> > When the `git config --global --help` command is invoked,\n> > the cli documentation is shown in the terminal with a small\n> > error in one of the values of the Type group, which is the\n> > absence of the type flag in the `--type` argument.\n> > This commit fixes that.\n>\n> What about the commit message below?\n>\n> ```\n> The usage help for --type option of `git config` is missing `type`\n> in the argument placeholder (`<>`). Add it.\n> ```\n\nThis commit message just got better, thanks. I will update with this message.\n\n> > - OPT_CALLBACK('t', \"type\", &type, \"\", N_(\"value is given this type\"), option_parse_type),\n> > + OPT_CALLBACK('t', \"type\", &type, N_(\"type\"), N_(\"value is given this type\"), option_parse_type),\n>\n> The help should be `give the value the specified type`.\n\nAbout the help message, I believe the current one is adequate, as Junio C Hamano well described.\n\nIt is also worth remembering that PR proposes a change from \"\" to \"type\" only, as recalled by Ævar Arnfjörð Bjarmason.\n\n"},{"id":"450354","messageId":"pull.1220.v2.git.git.1646368313714.gitgitgadget@gmail.com","threadId":"57478","inReplyTo":"pull.1220.git.git.1645853661519.gitgitgadget@gmail.com","subject":"[PATCH v2] fix: include the type flag in the cli docs","fromName":"Matheus Felipe via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2022-03-04T04:31:53Z","receivedAt":"2022-03-04T04:32:01Z","isPatch":true,"sender":{"key":"matheusfelipeog@protonmail.com","avatar":"https://avatars.githubusercontent.com/u/50463866?v=4"},"body":"From: Matheus Felipe <matheusfelipeog@protonmail.com>\n\nThe usage help for --type option of `git config` is missing `type`\nin the argument placeholder (`<>`). Add it.\n\nSigned-off-by: Matheus Felipe <matheusfelipeog@protonmail.com>\n---\n    fix: include the type flag in the cli docs\n    \n    When the git config --global --help command is invoked, the cli\n    documentation is shown in the terminal with a small error in one of the\n    values of the Type group, which is the absence of the type flag in the\n    --type argument:\n    \n    image\n    [https://user-images.githubusercontent.com/50463866/155674905-01fcdf18-8f67-488a-b367-985040dfe57d.png]\n    \n    In the web documentation and man page:\n    \n    image\n    [https://user-images.githubusercontent.com/50463866/155675353-4a39965a-875c-475c-829d-7849a982f5b9.png]\n    image\n    [https://user-images.githubusercontent.com/50463866/155675437-7283dbac-fff2-44b7-8733-7d5af375bce4.png]\n    \n    ------------------------------------------------------------------------\n    \n    Changes since v1:\n    \n     * Added a better commit message (as suggested by Bagas Sanjaya\n       <bagasdotme@gmail.com>)\n    \n    ------------------------------------------------------------------------\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1220%2Fmatheusfelipeog%2Ffix%2Fgit-config-docs-v2\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1220/matheusfelipeog/fix/git-config-docs-v2\nPull-Request: https://github.com/git/git/pull/1220\n\nRange-diff vs v1:\n\n 1:  7bc0abde8ff ! 1:  1550d29f5da fix: include the type flag in the cli docs\n     @@ Metadata\n       ## Commit message ##\n          fix: include the type flag in the cli docs\n      \n     -    When the `git config --global --help` command is invoked,\n     -    the cli documentation is shown in the terminal with a small\n     -    error in one of the values of the Type group, which is the\n     -    absence of the type flag in the `--type` argument.\n     -    This commit fixes that.\n     +    The usage help for --type option of `git config` is missing `type`\n     +    in the argument placeholder (`<>`). Add it.\n      \n          Signed-off-by: Matheus Felipe <matheusfelipeog@protonmail.com>\n      \n\n\n builtin/config.c | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/builtin/config.c b/builtin/config.c\nindex 542d8d02b2b..2aea465466b 100644\n--- a/builtin/config.c\n+++ b/builtin/config.c\n@@ -151,7 +151,7 @@ static struct option builtin_config_options[] = {\n \tOPT_BIT(0, \"get-color\", &actions, N_(\"find the color configured: slot [default]\"), ACTION_GET_COLOR),\n \tOPT_BIT(0, \"get-colorbool\", &actions, N_(\"find the color setting: slot [stdout-is-tty]\"), ACTION_GET_COLORBOOL),\n \tOPT_GROUP(N_(\"Type\")),\n-\tOPT_CALLBACK('t', \"type\", &type, \"\", N_(\"value is given this type\"), option_parse_type),\n+\tOPT_CALLBACK('t', \"type\", &type, N_(\"type\"), N_(\"value is given this type\"), option_parse_type),\n \tOPT_CALLBACK_VALUE(0, \"bool\", &type, N_(\"value is \\\"true\\\" or \\\"false\\\"\"), TYPE_BOOL),\n \tOPT_CALLBACK_VALUE(0, \"int\", &type, N_(\"value is decimal number\"), TYPE_INT),\n \tOPT_CALLBACK_VALUE(0, \"bool-or-int\", &type, N_(\"value is --bool or --int\"), TYPE_BOOL_OR_INT),\n\nbase-commit: dab1b7905d0b295f1acef9785bb2b9cbb0fdec84\n-- \ngitgitgadget\n"},{"id":"450362","messageId":"xmqq8rtq2may.fsf@gitster.g","threadId":"57478","inReplyTo":"pull.1220.v2.git.git.1646368313714.gitgitgadget@gmail.com","subject":"Re: [PATCH v2] fix: include the type flag in the cli docs","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-03-04T07:45:25Z","receivedAt":"2022-03-04T07:45:30Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Matheus Felipe via GitGitGadget\" <gitgitgadget@gmail.com> writes:\n\n> Subject: Re: [PATCH v2] fix: include the type flag in the cli docs\n\nOne more (hopefully final) nit.  By reading the above alone (which\nis what people will see in \"git shortlog --no-merges\" output), you\ncan not even guess which subcommand the \"fix\" is about, or if it is\neven a fix to the code, or just a documentation update.\n\nI'd retitle it to\n\n\tconfig: correct \"--type\" option in \"git config -h\" output\n\n> From: Matheus Felipe <matheusfelipeog@protonmail.com>\n>\n> The usage help for --type option of `git config` is missing `type`\n> in the argument placeholder (`<>`). Add it.\n\nGood.\n\n> diff --git a/builtin/config.c b/builtin/config.c\n> index 542d8d02b2b..2aea465466b 100644\n> --- a/builtin/config.c\n> +++ b/builtin/config.c\n> @@ -151,7 +151,7 @@ static struct option builtin_config_options[] = {\n>  \tOPT_BIT(0, \"get-color\", &actions, N_(\"find the color configured: slot [default]\"), ACTION_GET_COLOR),\n>  \tOPT_BIT(0, \"get-colorbool\", &actions, N_(\"find the color setting: slot [stdout-is-tty]\"), ACTION_GET_COLORBOOL),\n>  \tOPT_GROUP(N_(\"Type\")),\n> -\tOPT_CALLBACK('t', \"type\", &type, \"\", N_(\"value is given this type\"), option_parse_type),\n> +\tOPT_CALLBACK('t', \"type\", &type, N_(\"type\"), N_(\"value is given this type\"), option_parse_type),\n\nGood again.\n\nThanks.  Will queue.\n"},{"id":"450412","messageId":"wPjDF_MqZ9RmGuEcyP_8axDVW9K7gfBaiycvgu6MM0UeW2ovCLDD5PqOVf7Q56aNGdFqaKUQvnOsoPW_0lj7matX-HmMGaL-uwhE8hrcPyA=@protonmail.com","threadId":"57478","inReplyTo":"xmqq8rtq2may.fsf@gitster.g","subject":"Re: [PATCH v2] fix: include the type flag in the cli docs","fromName":"Matheus Felipe","fromEmail":"matheusfelipeog@protonmail.com","sentAt":"2022-03-04T15:52:51Z","receivedAt":"2022-03-04T15:53:05Z","isPatch":true,"sender":{"key":"matheusfelipeog@protonmail.com","avatar":"https://avatars.githubusercontent.com/u/50463866?v=4"},"body":"> One more (hopefully final) nit. By reading the above alone (which\n> is what people will see in \"git shortlog --no-merges\" output), you\n> can not even guess which subcommand the \"fix\" is about, or if it is\n> even a fix to the code, or just a documentation update.\n>\n> I'd retitle it to\n>\n> config: correct \"--type\" option in \"git config -h\" output\n\nYou are right, this title is much better. I will update it.\n\nThank you very much, I learned a few things from this contribution.\n\n"},{"id":"450413","messageId":"pull.1220.v3.git.git.1646410557888.gitgitgadget@gmail.com","threadId":"57478","inReplyTo":"pull.1220.v2.git.git.1646368313714.gitgitgadget@gmail.com","subject":"[PATCH v3] config: correct \"--type\" option in \"git config -h\" output","fromName":"Matheus Felipe via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2022-03-04T16:15:57Z","receivedAt":"2022-03-04T16:16:14Z","isPatch":true,"sender":{"key":"matheusfelipeog@protonmail.com","avatar":"https://avatars.githubusercontent.com/u/50463866?v=4"},"body":"From: Matheus Felipe <matheusfelipeog@protonmail.com>\n\nThe usage help for --type option of `git config` is missing `type`\nin the argument placeholder (`<>`). Add it.\n\nSigned-off-by: Matheus Felipe <matheusfelipeog@protonmail.com>\n---\n    config: correct \"--type\" option in \"git config -h\" output\n    \n    When the git config --global --help command is invoked, the cli\n    documentation is shown in the terminal with a small error in one of the\n    values of the Type group, which is the absence of the type flag in the\n    --type argument:\n    \n    image\n    [https://user-images.githubusercontent.com/50463866/155674905-01fcdf18-8f67-488a-b367-985040dfe57d.png]\n    \n    In the web documentation and man page:\n    \n    image\n    [https://user-images.githubusercontent.com/50463866/155675353-4a39965a-875c-475c-829d-7849a982f5b9.png]\n    image\n    [https://user-images.githubusercontent.com/50463866/155675437-7283dbac-fff2-44b7-8733-7d5af375bce4.png]\n    \n    ------------------------------------------------------------------------\n    \n    Changes since v1:\n    \n     * Added a better commit message (as suggested by Bagas Sanjaya\n       <bagasdotme@gmail.com>)\n     * Improve the title of the commit, to make it more explicit when viewed\n       with git shortlog --no-merges (as suggested by Junio C Hamano\n       <gitster@pobox.com>)\n    \n    ------------------------------------------------------------------------\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1220%2Fmatheusfelipeog%2Ffix%2Fgit-config-docs-v3\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1220/matheusfelipeog/fix/git-config-docs-v3\nPull-Request: https://github.com/git/git/pull/1220\n\nRange-diff vs v2:\n\n 1:  1550d29f5da ! 1:  f0fff5f3597 fix: include the type flag in the cli docs\n     @@ Metadata\n      Author: Matheus Felipe <matheusfelipeog@protonmail.com>\n      \n       ## Commit message ##\n     -    fix: include the type flag in the cli docs\n     +    config: correct \"--type\" option in \"git config -h\" output\n      \n          The usage help for --type option of `git config` is missing `type`\n          in the argument placeholder (`<>`). Add it.\n\n\n builtin/config.c | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/builtin/config.c b/builtin/config.c\nindex 542d8d02b2b..2aea465466b 100644\n--- a/builtin/config.c\n+++ b/builtin/config.c\n@@ -151,7 +151,7 @@ static struct option builtin_config_options[] = {\n \tOPT_BIT(0, \"get-color\", &actions, N_(\"find the color configured: slot [default]\"), ACTION_GET_COLOR),\n \tOPT_BIT(0, \"get-colorbool\", &actions, N_(\"find the color setting: slot [stdout-is-tty]\"), ACTION_GET_COLORBOOL),\n \tOPT_GROUP(N_(\"Type\")),\n-\tOPT_CALLBACK('t', \"type\", &type, \"\", N_(\"value is given this type\"), option_parse_type),\n+\tOPT_CALLBACK('t', \"type\", &type, N_(\"type\"), N_(\"value is given this type\"), option_parse_type),\n \tOPT_CALLBACK_VALUE(0, \"bool\", &type, N_(\"value is \\\"true\\\" or \\\"false\\\"\"), TYPE_BOOL),\n \tOPT_CALLBACK_VALUE(0, \"int\", &type, N_(\"value is decimal number\"), TYPE_INT),\n \tOPT_CALLBACK_VALUE(0, \"bool-or-int\", &type, N_(\"value is --bool or --int\"), TYPE_BOOL_OR_INT),\n\nbase-commit: dab1b7905d0b295f1acef9785bb2b9cbb0fdec84\n-- \ngitgitgadget\n"}]}