# [PATCH] doc: fix repo_config documentation reference 5 messages from 2026-02-05 to 2026-02-06. Participants: Soutrik Das via GitGitGadget, Shreyansh Paliwal, SoutrikDas, Junio C Hamano. Thread: https://gitlist.dev/t/64926 ## Soutrik Das via GitGitGadget, 2026-02-05 12:03 Subject: [PATCH] doc: fix repo_config documentation reference Message-ID: URL: https://gitlist.dev/e/pull.2187.git.git.1770293021383.gitgitgadget%40gmail.com ``` From: SoutrikDas Since documentation was moved from Documenation/ technical/api-config to inside the config.h This might help newcomers, by pointing them to the right place to get documentation about repo_config Signed-off-by: SoutrikDas --- doc: fix repo_config documentation reference Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2187%2FSoutrikDas%2Fdoc-fix-myfirstcontribution-config-ref-v1 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2187/SoutrikDas/doc-fix-myfirstcontribution-config-ref-v1 Pull-Request: https://github.com/git/git/pull/2187 Documentation/MyFirstContribution.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc index f186dfbc89..92de476a7f 100644 --- a/Documentation/MyFirstContribution.adoc +++ b/Documentation/MyFirstContribution.adoc @@ -351,7 +351,7 @@ function body: apply standard precedence rules. `repo_config_get_string_tmp()` will look up a specific key ("user.name") and give you the value. There are a number of single-key lookup functions like this one; you can see them all (and more info -about how to use `repo_config()`) in `Documentation/technical/api-config.adoc`. +about how to use `repo_config()`) in `config.h`. You should see that the name printed matches the one you see when you run: base-commit: b2826b52eb7caff9f4ed6e85ec45e338bf02ad09 -- gitgitgadget ``` ## Shreyansh Paliwal, 2026-02-05 13:11 Subject: Re: [PATCH] doc: fix repo_config documentation reference Message-ID: <20260205131132.44282-1-shreyanshpaliwalcmsmn@gmail.com> URL: https://gitlist.dev/e/20260205131132.44282-1-shreyanshpaliwalcmsmn%40gmail.com In-Reply-To: ``` > Since documentation was moved from Documenation/ > technical/api-config to inside the config.h > This might help newcomers, by pointing them to the > right place to get documentation about repo_config Some suggestions, * s/Documenation/Documentation * ~70 cols is the practical followed line wrapping, so you can follow that for best readability. * First describe the current problem statement which describes the current state in the present tense like, In MyFirstContribution.adoc, the link to the repo_config() documentation is invalid because the documentation related was moved to a different file. * Then you instruct somebody to make changes to the code to make it better like, Replace the path for the repo_config() documentation from 'Documenation/technical/api-config' to 'config.h'. * Then you can state your additional explainations, references and/or advantages, whatever seems relevant for the change you just stated. Best, Shreyansh ``` ## SoutrikDas, 2026-02-06 06:01 Subject: Re: [PATCH] doc: fix repo_config documentation reference Message-ID: <20260206060156.73753-1-valusoutrik@gmail.com> URL: https://gitlist.dev/e/20260206060156.73753-1-valusoutrik%40gmail.com In-Reply-To: <20260205131132.44282-1-shreyanshpaliwalcmsmn@gmail.com> ``` - Documenation spelling corrected > First describe the current problem statement which describes the > current state in the present tense like > "In MyFirstContribution.adoc, the link to the repo_config() > documentation is invalid because the documentation related was > moved to a different file." Let this be A > Then you instruct somebody to make changes to the code to make it > better like > Replace the path for the repo_config() documentation from > 'Documentation/technical/api-config' to 'config.h'. Let this be B So the Commit will be > > > And the cover mail for that patch will be > > > > > I configured my git send-email because I couldnt reply to your email with gitgitgadget ... maybe it was my mistake. Anyway I wanted to ask Now that I have changed the commit message , what should I do ? Should I send a [PATCH v2] as a seperate thread or send it here ? ``` ## SoutrikDas, 2026-02-06 06:21 Subject: [GSOC PATCH v2] doc: fix repo_config documentation reference Message-ID: <20260206062108.74072-1-valusoutrik@gmail.com> URL: https://gitlist.dev/e/20260206062108.74072-1-valusoutrik%40gmail.com In-Reply-To: <20260206060156.73753-1-valusoutrik@gmail.com> ``` In MyFirstContribution.adoc, the link to the repo_config() documentation is invalid because the related documentation was moved to a different file. Replace the path for the repo_config() documentation from 'Documentation/technical/api-config.h' to 'config.h'. Signed-off-by: SoutrikDas --- Changes from v1 : Corrected Documentation Spelling Added .h after api-config Changed Commit message to suit git's style --- Documentation/MyFirstContribution.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc index f186dfbc89..92de476a7f 100644 --- a/Documentation/MyFirstContribution.adoc +++ b/Documentation/MyFirstContribution.adoc @@ -351,7 +351,7 @@ function body: apply standard precedence rules. `repo_config_get_string_tmp()` will look up a specific key ("user.name") and give you the value. There are a number of single-key lookup functions like this one; you can see them all (and more info -about how to use `repo_config()`) in `Documentation/technical/api-config.adoc`. +about how to use `repo_config()`) in `config.h`. You should see that the name printed matches the one you see when you run: -- 2.50.1 (Apple Git-155) ``` ## Junio C Hamano, 2026-02-06 16:39 Subject: Re: [GSOC PATCH v2] doc: fix repo_config documentation reference Message-ID: URL: https://gitlist.dev/e/xmqqfr7dhln9.fsf%40gitster.g In-Reply-To: <20260206062108.74072-1-valusoutrik@gmail.com> ``` SoutrikDas writes: > In MyFirstContribution.adoc, the link to the repo_config() > documentation is invalid because the related documentation was moved > to a different file. > > Replace the path for the repo_config() documentation from > 'Documentation/technical/api-config.h' to 'config.h'. OK. I eyeballed output from $ git grep 'Documentation/technical/.*\.adoc' Documentation/ and everything else mentioned are still there. Thanks. > > Signed-off-by: SoutrikDas > --- > Changes from v1 : > Corrected Documentation Spelling > Added .h after api-config > Changed Commit message to suit git's style > --- > Documentation/MyFirstContribution.adoc | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc > index f186dfbc89..92de476a7f 100644 > --- a/Documentation/MyFirstContribution.adoc > +++ b/Documentation/MyFirstContribution.adoc > @@ -351,7 +351,7 @@ function body: > apply standard precedence rules. `repo_config_get_string_tmp()` will look up > a specific key ("user.name") and give you the value. There are a number of > single-key lookup functions like this one; you can see them all (and more info > -about how to use `repo_config()`) in `Documentation/technical/api-config.adoc`. > +about how to use `repo_config()`) in `config.h`. > > You should see that the name printed matches the one you see when you run: ```