From: "Ophir Bleicher via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Ophir Bleicher <ophirble@gmail.com>, Ophir Bleicher <ophirble@gmail.com>
Subject: [PATCH v2] doc: update README file name in my first contribution
Date: Fri, 20 Nov 2026 18:31:23 +0000 [thread overview]
Message-ID: <pull.2495.v2.git.git.1795199483155.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2495.git.git.1795194253192.gitgitgadget@gmail.com>
From: Ophir Bleicher <ophirble@gmail.com>
The translation notice in MyFirstContribution.adoc references
po/README, but the actual file name is po/README.md.
Change it to po/README.md.
Signed-off-by: Ophir Bleicher <ophirble@gmail.com>
---
doc: update README file name in my first contribution
The translation notice in MyFirstContribution.adoc referenced po/README,
but the actual file name is po/README.md. Changed it to po/README.md.
Changes from v1:
* Update commit message grammatical syntax
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2495%2FOphirBleicher%2Fpatch-2-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2495/OphirBleicher/patch-2-v2
Pull-Request: https://github.com/git/git/pull/2495
Range-diff vs v1:
1: 4e8ec81b21 ! 1: 11905ef191 doc: update README file name in my first contribution
@@ Metadata
## Commit message ##
doc: update README file name in my first contribution
- The translation notice in MyFirstContribution.adoc referenced
+ The translation notice in MyFirstContribution.adoc references
po/README, but the actual file name is po/README.md.
- Changed it to po/README.md.
+
+ Change it to po/README.md.
Signed-off-by: Ophir Bleicher <ophirble@gmail.com>
Documentation/MyFirstContribution.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc
index c58253fd54..29dc402e5a 100644
--- a/Documentation/MyFirstContribution.adoc
+++ b/Documentation/MyFirstContribution.adoc
@@ -186,7 +186,7 @@ decent starting point as we can now add build rules and register the command.
NOTE: Your throwaway text, as well as much of the text you will be adding over
the course of this tutorial, is user-facing. That means it needs to be
-localizable. Take a look at `po/README` under "Marking strings for translation".
+localizable. Take a look at `po/README.md` under "Marking strings for translation".
Throughout the tutorial, we will mark strings for translation as necessary; you
should also do so when writing your user-facing commands in the future.
base-commit: f7de81456940dd6f3274e461149bba12965de609
--
gitgitgadget
prev parent reply other threads:[~2026-11-20 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 17:04 [PATCH] doc: update README file name in my first contribution Ophir Bleicher via GitGitGadget
2026-11-20 18:24 ` Junio C Hamano
2026-11-20 18:31 ` Ophir Bleicher via GitGitGadget [this message]
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=pull.2495.v2.git.git.1795199483155.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=ophirble@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.