# [PATCH] doc: fix typo in submitting patches 2 messages from 2026-08-14 to 2026-08-14. Participants: Swapnil Saste | INDIA via GitGitGadget, Junio C Hamano. Thread: https://gitlist.dev/t/66175 ## Swapnil Saste | INDIA via GitGitGadget, 2026-08-14 18:46 Subject: [PATCH] doc: fix typo in submitting patches Message-ID: ``` From: Swapnil Saste | INDIA Remove the article "an" before "incremental updates". Signed-off-by: Swapnil Saste | INDIA --- 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 ``` ## Junio C Hamano, 2026-08-14 19:20 Subject: Re: [PATCH] doc: fix typo in submitting patches Message-ID: In-Reply-To: ``` "Swapnil Saste | INDIA via GitGitGadget" writes: > From: Swapnil Saste | INDIA > > Remove the article "an" before "incremental updates". Thanks, will apply. > > Signed-off-by: Swapnil Saste | INDIA > --- > 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 ```