{"thread":{"id":"53025","subject":"[PATCH] RelNotes/2.26.0: fix various typos","startedAt":"2020-03-18T21:18:30Z","lastAt":"2020-03-18T22:42:28Z","messageCount":2,"participants":["Elijah Newren via GitGitGadget","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"393420","messageId":"pull.731.git.git.1584566306427.gitgitgadget@gmail.com","threadId":"53025","inReplyTo":null,"subject":"[PATCH] RelNotes/2.26.0: fix various typos","fromName":"Elijah Newren via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2020-03-18T21:18:26Z","receivedAt":"2020-03-18T21:18:30Z","isPatch":true,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"From: Elijah Newren <newren@gmail.com>\n\nSigned-off-by: Elijah Newren <newren@gmail.com>\n---\n    RelNotes/2.26.0: fix various typos\n    \n    gitgitgadget requires a description even though for single-commit series\n    it doesn't use it to generate a cover letter. So now there's some\n    useless text between the commit message and diff. Sorry.\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-731%2Fnewren%2Frelnotes-typos-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-731/newren/relnotes-typos-v1\nPull-Request: https://github.com/git/git/pull/731\n\n Documentation/RelNotes/2.26.0.txt | 8 ++++----\n 1 file changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/RelNotes/2.26.0.txt b/Documentation/RelNotes/2.26.0.txt\nindex 719750dbb5f..3a7a734c269 100644\n--- a/Documentation/RelNotes/2.26.0.txt\n+++ b/Documentation/RelNotes/2.26.0.txt\n@@ -8,7 +8,7 @@ Backward compatibility notes\n \n  * \"git rebase\" uses a different backend that is based on the 'merge'\n    machinery by default.  There are a few known differences in the\n-   behaviour from the traditional machniery based on patch+apply.\n+   behaviour from the traditional machinery based on patch+apply.\n \n    If your workflow is negatively affected by this change, please\n    report it to git@vger.kernel.org so that we can take a look into\n@@ -63,7 +63,7 @@ UI, Workflows & Features\n  * \"git rm\" and \"git stash\" learns the new \"--pathspec-from-file\"\n    option.\n \n- * \"git am --short-current-patch\" is a way to show the piece of e-mail\n+ * \"git am --show-current-patch\" is a way to show the piece of e-mail\n    for the stopped step, which is not suitable to directly feed \"git\n    apply\" (it is designed to be a good \"git am\" input).  It learned a\n    new option to show only the patch part.\n@@ -79,7 +79,7 @@ Performance, Internal Implementation, Development Support etc.\n    with tabs.\n \n  * The test-lint machinery knew to check \"VAR=VAL shell_function\"\n-   construct, but did not check \"VAR= shell_funciton\", which has been\n+   construct, but did not check \"VAR= shell_function\", which has been\n    corrected.\n \n  * Replace \"git config --bool\" calls with \"git config --type=bool\" in\n@@ -229,7 +229,7 @@ Fixes since v2.25\n  * Unhelpful warning messages during documentation build have been squelched.\n \n  * \"git rebase -i\" identifies existing commits in its todo file with\n-   their abbreviated object name, which could become ambigous as it\n+   their abbreviated object name, which could become ambiguous as it\n    goes to create new commits, and has a mechanism to avoid ambiguity\n    in the main part of its execution.  A few other cases however were\n    not covered by the protection against ambiguity, which has been\n\nbase-commit: be8661a3286c67a5d4088f4226cbd7f8b76544b0\n-- \ngitgitgadget\n"},{"id":"393425","messageId":"xmqqzhcde14k.fsf@gitster.c.googlers.com","threadId":"53025","inReplyTo":"pull.731.git.git.1584566306427.gitgitgadget@gmail.com","subject":"Re: [PATCH] RelNotes/2.26.0: fix various typos","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-03-18T22:42:19Z","receivedAt":"2020-03-18T22:42:28Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thanks.\n"}]}