From: "Swapnil Saste | INDIA via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Swapnil Saste | INDIA <theswapnilsaste@gmail.Com>,
Swapnil Saste | INDIA <theswapnilsaste@gmail.Com>
Subject: [PATCH] doc: fix typo in submitting patches
Date: Fri, 14 Aug 2026 18:46:59 +0000 [thread overview]
Message-ID: <pull.2383.git.git.1786733219160.gitgitgadget@gmail.com> (raw)
From: Swapnil Saste | INDIA <theswapnilsaste@gmail.Com>
Remove the article "an" before "incremental updates".
Signed-off-by: Swapnil Saste | INDIA <theswapnilsaste@gmail.Com>
---
doc: fix typo in submitting patches
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2383%2FtheSwapnilSaste%2Ffix-typo-in-SubmittingPatches-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2383/theSwapnilSaste/fix-typo-in-SubmittingPatches-v1
Pull-Request: https://github.com/git/git/pull/2383
Documentation/SubmittingPatches | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index c269e474e3..c60855f706 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -117,7 +117,7 @@ of review.
can still continue to further improve them by adding more patches on
top, but by the time a topic gets merged to 'next', it is expected
that everybody agrees that the scope and the basic direction of the
- topic are appropriate, so such an incremental updates are limited to
+ topic are appropriate, so such incremental updates are limited to
small corrections and polishing. After a topic cooks for some time
(like 7 calendar days) in 'next' without needing further tweaks on
top, it gets merged to the 'master' branch and waits to become part
base-commit: 745601a9a94110d74769ab605ccd4f61339758d2
--
gitgitgadget
next reply other threads:[~2026-08-14 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 18:46 Swapnil Saste | INDIA via GitGitGadget [this message]
2026-08-14 19:20 ` [PATCH] doc: fix typo in submitting patches 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=pull.2383.git.git.1786733219160.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=theswapnilsaste@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