{"thread":{"id":"64926","subject":"[PATCH] doc: fix repo_config documentation reference","startedAt":"2026-02-05T12:03:45Z","lastAt":"2026-02-06T16:39:08Z","messageCount":5,"participants":["Soutrik Das via GitGitGadget","Shreyansh Paliwal","SoutrikDas","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"535232","messageId":"pull.2187.git.git.1770293021383.gitgitgadget@gmail.com","threadId":"64926","inReplyTo":null,"subject":"[PATCH] doc: fix repo_config documentation reference","fromName":"Soutrik Das via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2026-02-05T12:03:41Z","receivedAt":"2026-02-05T12:03:45Z","isPatch":true,"sender":{"key":"name:Soutrik Das","avatar":null},"body":"From: SoutrikDas <valusoutrik@gmail.com>\n\nSince documentation was moved from Documenation/\ntechnical/api-config to inside the config.h\nThis might help newcomers, by pointing them to the\nright place to get documentation about repo_config\n\nSigned-off-by: SoutrikDas <valusoutrik@gmail.com>\n---\n    doc: fix repo_config documentation reference\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2187%2FSoutrikDas%2Fdoc-fix-myfirstcontribution-config-ref-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2187/SoutrikDas/doc-fix-myfirstcontribution-config-ref-v1\nPull-Request: https://github.com/git/git/pull/2187\n\n Documentation/MyFirstContribution.adoc | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\nindex f186dfbc89..92de476a7f 100644\n--- a/Documentation/MyFirstContribution.adoc\n+++ b/Documentation/MyFirstContribution.adoc\n@@ -351,7 +351,7 @@ function body:\n apply standard precedence rules. `repo_config_get_string_tmp()` will look up\n a specific key (\"user.name\") and give you the value. There are a number of\n single-key lookup functions like this one; you can see them all (and more info\n-about how to use `repo_config()`) in `Documentation/technical/api-config.adoc`.\n+about how to use `repo_config()`) in `config.h`.\n \n You should see that the name printed matches the one you see when you run:\n \n\nbase-commit: b2826b52eb7caff9f4ed6e85ec45e338bf02ad09\n-- \ngitgitgadget\n"},{"id":"535239","messageId":"20260205131132.44282-1-shreyanshpaliwalcmsmn@gmail.com","threadId":"64926","inReplyTo":"pull.2187.git.git.1770293021383.gitgitgadget@gmail.com","subject":"Re: [PATCH] doc: fix repo_config documentation reference","fromName":"Shreyansh Paliwal","fromEmail":"shreyanshpaliwalcmsmn@gmail.com","sentAt":"2026-02-05T13:11:25Z","receivedAt":"2026-02-05T13:11:41Z","isPatch":true,"sender":{"key":"shreyanshpaliwalcmsmn@gmail.com","avatar":"https://avatars.githubusercontent.com/u/152720574?v=4"},"body":"> Since documentation was moved from Documenation/\n> technical/api-config to inside the config.h\n> This might help newcomers, by pointing them to the\n> right place to get documentation about repo_config\n\nSome suggestions,\n\n* s/Documenation/Documentation\n\n* ~70 cols is the practical followed line wrapping, so you can follow that\nfor best readability.\n\n* First describe the current problem statement which describes the\ncurrent state in the present tense like,\n\n   In MyFirstContribution.adoc, the link to the repo_config()\n   documentation is invalid because the documentation related was moved\n   to a different file.\n\n* Then you instruct somebody to make changes to the code to make it better like,\n\n   Replace the path for the repo_config() documentation from\n   'Documenation/technical/api-config' to 'config.h'.\n\n* Then you can state your additional explainations, references and/or\nadvantages, whatever seems relevant for the change you just stated.\n\nBest,\nShreyansh\n"},{"id":"535309","messageId":"20260206060156.73753-1-valusoutrik@gmail.com","threadId":"64926","inReplyTo":"20260205131132.44282-1-shreyanshpaliwalcmsmn@gmail.com","subject":"Re: [PATCH] doc: fix repo_config documentation reference","fromName":"SoutrikDas","fromEmail":"valusoutrik@gmail.com","sentAt":"2026-02-06T06:01:56Z","receivedAt":"2026-02-06T06:02:03Z","isPatch":true,"sender":{"key":"valusoutrik@gmail.com","avatar":"https://avatars.githubusercontent.com/u/56778179?v=4"},"body":"- Documenation spelling corrected\n\n> First describe the current problem statement which describes the \n> current state in the present tense like \n> \"In MyFirstContribution.adoc, the link to the repo_config() \n> documentation is invalid because the documentation related was \n> moved to a different file.\"\n\nLet this be A \n\n> Then you instruct somebody to make changes to the code to make it \n> better like \n> Replace the path for the repo_config() documentation from \n> 'Documentation/technical/api-config' to 'config.h'.\n\nLet this be B\n\nSo the Commit will be \n> <short tile> \n> \n> <B> \n\nAnd the cover mail for that patch will be \n> <short tile same as commit message ? > \n> \n> <A>\n>\n> <B> \n\nI configured my git send-email because I couldnt reply to your email\nwith gitgitgadget ... maybe it was my mistake. Anyway I wanted to ask\nNow that I have changed the commit message , what should I do ? \nShould I send a [PATCH v2] as a seperate thread or send it here ?\n\n"},{"id":"535310","messageId":"20260206062108.74072-1-valusoutrik@gmail.com","threadId":"64926","inReplyTo":"20260206060156.73753-1-valusoutrik@gmail.com","subject":"[GSOC PATCH v2] doc: fix repo_config documentation reference","fromName":"SoutrikDas","fromEmail":"valusoutrik@gmail.com","sentAt":"2026-02-06T06:21:08Z","receivedAt":"2026-02-06T06:21:16Z","isPatch":true,"sender":{"key":"valusoutrik@gmail.com","avatar":"https://avatars.githubusercontent.com/u/56778179?v=4"},"body":"In MyFirstContribution.adoc, the link to the repo_config() \ndocumentation is invalid because the related documentation was moved \nto a different file.\n\nReplace the path for the repo_config() documentation from\n'Documentation/technical/api-config.h' to 'config.h'.\n\nSigned-off-by: SoutrikDas <valusoutrik@gmail.com>\n---\nChanges from v1 : \nCorrected Documentation Spelling\nAdded .h after api-config\nChanged Commit message to suit git's style\n---\n Documentation/MyFirstContribution.adoc | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\nindex f186dfbc89..92de476a7f 100644\n--- a/Documentation/MyFirstContribution.adoc\n+++ b/Documentation/MyFirstContribution.adoc\n@@ -351,7 +351,7 @@ function body:\n apply standard precedence rules. `repo_config_get_string_tmp()` will look up\n a specific key (\"user.name\") and give you the value. There are a number of\n single-key lookup functions like this one; you can see them all (and more info\n-about how to use `repo_config()`) in `Documentation/technical/api-config.adoc`.\n+about how to use `repo_config()`) in `config.h`.\n \n You should see that the name printed matches the one you see when you run:\n \n-- \n2.50.1 (Apple Git-155)\n\n"},{"id":"535366","messageId":"xmqqfr7dhln9.fsf@gitster.g","threadId":"64926","inReplyTo":"20260206062108.74072-1-valusoutrik@gmail.com","subject":"Re: [GSOC PATCH v2] doc: fix repo_config documentation reference","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-02-06T16:39:06Z","receivedAt":"2026-02-06T16:39:08Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"SoutrikDas <valusoutrik@gmail.com> writes:\n\n> In MyFirstContribution.adoc, the link to the repo_config() \n> documentation is invalid because the related documentation was moved \n> to a different file.\n>\n> Replace the path for the repo_config() documentation from\n> 'Documentation/technical/api-config.h' to 'config.h'.\n\nOK.  I eyeballed output from\n\n    $ git grep 'Documentation/technical/.*\\.adoc' Documentation/\n\nand everything else mentioned are still there.\n\nThanks.\n\n>\n> Signed-off-by: SoutrikDas <valusoutrik@gmail.com>\n> ---\n> Changes from v1 : \n> Corrected Documentation Spelling\n> Added .h after api-config\n> Changed Commit message to suit git's style\n> ---\n>  Documentation/MyFirstContribution.adoc | 2 +-\n>  1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n> index f186dfbc89..92de476a7f 100644\n> --- a/Documentation/MyFirstContribution.adoc\n> +++ b/Documentation/MyFirstContribution.adoc\n> @@ -351,7 +351,7 @@ function body:\n>  apply standard precedence rules. `repo_config_get_string_tmp()` will look up\n>  a specific key (\"user.name\") and give you the value. There are a number of\n>  single-key lookup functions like this one; you can see them all (and more info\n> -about how to use `repo_config()`) in `Documentation/technical/api-config.adoc`.\n> +about how to use `repo_config()`) in `config.h`.\n>  \n>  You should see that the name printed matches the one you see when you run:\n"}]}