git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>, Elijah Newren <newren@gmail.com>
Subject: [PATCH] RelNotes/2.26.0: fix various typos
Date: Wed, 18 Mar 2020 21:18:26 +0000	[thread overview]
Message-ID: <pull.731.git.git.1584566306427.gitgitgadget@gmail.com> (raw)

From: Elijah Newren <newren@gmail.com>

Signed-off-by: Elijah Newren <newren@gmail.com>
---
    RelNotes/2.26.0: fix various typos
    
    gitgitgadget requires a description even though for single-commit series
    it doesn't use it to generate a cover letter. So now there's some
    useless text between the commit message and diff. Sorry.

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-731%2Fnewren%2Frelnotes-typos-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-731/newren/relnotes-typos-v1
Pull-Request: https://github.com/git/git/pull/731

 Documentation/RelNotes/2.26.0.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/RelNotes/2.26.0.txt b/Documentation/RelNotes/2.26.0.txt
index 719750dbb5f..3a7a734c269 100644
--- a/Documentation/RelNotes/2.26.0.txt
+++ b/Documentation/RelNotes/2.26.0.txt
@@ -8,7 +8,7 @@ Backward compatibility notes
 
  * "git rebase" uses a different backend that is based on the 'merge'
    machinery by default.  There are a few known differences in the
-   behaviour from the traditional machniery based on patch+apply.
+   behaviour from the traditional machinery based on patch+apply.
 
    If your workflow is negatively affected by this change, please
    report it to git@vger.kernel.org so that we can take a look into
@@ -63,7 +63,7 @@ UI, Workflows & Features
  * "git rm" and "git stash" learns the new "--pathspec-from-file"
    option.
 
- * "git am --short-current-patch" is a way to show the piece of e-mail
+ * "git am --show-current-patch" is a way to show the piece of e-mail
    for the stopped step, which is not suitable to directly feed "git
    apply" (it is designed to be a good "git am" input).  It learned a
    new option to show only the patch part.
@@ -79,7 +79,7 @@ Performance, Internal Implementation, Development Support etc.
    with tabs.
 
  * The test-lint machinery knew to check "VAR=VAL shell_function"
-   construct, but did not check "VAR= shell_funciton", which has been
+   construct, but did not check "VAR= shell_function", which has been
    corrected.
 
  * Replace "git config --bool" calls with "git config --type=bool" in
@@ -229,7 +229,7 @@ Fixes since v2.25
  * Unhelpful warning messages during documentation build have been squelched.
 
  * "git rebase -i" identifies existing commits in its todo file with
-   their abbreviated object name, which could become ambigous as it
+   their abbreviated object name, which could become ambiguous as it
    goes to create new commits, and has a mechanism to avoid ambiguity
    in the main part of its execution.  A few other cases however were
    not covered by the protection against ambiguity, which has been

base-commit: be8661a3286c67a5d4088f4226cbd7f8b76544b0
-- 
gitgitgadget

             reply	other threads:[~2020-03-18 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 21:18 Elijah Newren via GitGitGadget [this message]
2020-03-18 22:42 ` [PATCH] RelNotes/2.26.0: fix various typos 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.731.git.git.1584566306427.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).