doc: fix typo in submitting patches
PATCH 1/1 doc: fix typo in submitting patches
From: Swapnil Saste | INDIA <[email protected]>
Remove the article "an" before "incremental updates".
---
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(-)
Documentation/SubmittingPatches +1 -1
@@ -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
Signature · 1 line
gitgitgadget
"Swapnil Saste | INDIA via GitGitGadget" <[email protected]>
Quoted 3 lines · writes:
From: Swapnil Saste | INDIA <[email protected]>
Remove the article "an" before "incremental updates".
Thanks, will apply.
Quoted 27 lines
Signed-off-by Swapnil Saste | INDIA <[email protected]>---
doc: fix typo in submitting patchesPublished-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/2383Documentation/SubmittingPatches | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/SubmittingPatches +1
-1@@ -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 partbase-commit:
745601a9a94110d74769ab605ccd4f61339758d2