From: SoutrikDas <valusoutrik@gmail.com>
To: valusoutrik@gmail.com
Cc: git@vger.kernel.org, shreyanshpaliwalcmsmn@gmail.com
Subject: [GSOC PATCH v2] doc: fix repo_config documentation reference
Date: Fri, 6 Feb 2026 11:51:08 +0530 [thread overview]
Message-ID: <20260206062108.74072-1-valusoutrik@gmail.com> (raw)
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 <valusoutrik@gmail.com>
---
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)
next prev parent reply other threads:[~2026-02-06 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 12:03 [PATCH] doc: fix repo_config documentation reference Soutrik Das via GitGitGadget
2026-02-05 13:11 ` Shreyansh Paliwal
2026-02-06 6:01 ` SoutrikDas
2026-02-06 6:21 ` SoutrikDas [this message]
2026-02-06 16:39 ` [GSOC PATCH v2] " Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260206062108.74072-1-valusoutrik@gmail.com \
--to=valusoutrik@gmail.com \
--cc=git@vger.kernel.org \
--cc=shreyanshpaliwalcmsmn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox