From: Taylor Blau <me@ttaylorr.com>
To: Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH 0/2] Typo fixes
Date: Tue, 28 Jul 2020 16:48:04 -0400 [thread overview]
Message-ID: <20200728204804.GA94132@syl.lan> (raw)
In-Reply-To: <pull.824.git.git.1595969139.gitgitgadget@gmail.com>
On Tue, Jul 28, 2020 at 08:45:37PM +0000, Elijah Newren via GitGitGadget wrote:
> Fix some simple typos: doubled words, and character swapping
Far be it from me--since I seem to always be making these mistakes
myself--to be an authoritative reviewer on this series, but it looks
obviously good to me ;-).
Reviewed-by: Taylor Blau <me@ttaylorr.com>
> Elijah Newren (2):
> Remove doubled words in various comments
> hashmap: fix typo in usage docs
>
> fsmonitor.c | 2 +-
> hashmap.h | 2 +-
> t/t5510-fetch.sh | 2 +-
> t/t6046-merge-skip-unneeded-updates.sh | 2 +-
> t/t8014-blame-ignore-fuzzy.sh | 2 +-
> wt-status.c | 2 +-
> 6 files changed, 6 insertions(+), 6 deletions(-)
>
>
> base-commit: 47ae905ffb98cc4d4fd90083da6bc8dab55d9ecc
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-824%2Fnewren%2Ftypo-fixes-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-824/newren/typo-fixes-v1
> Pull-Request: https://github.com/git/git/pull/824
> --
> gitgitgadget
Thanks,
Taylor
next prev parent reply other threads:[~2020-07-28 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 20:45 [PATCH 0/2] Typo fixes Elijah Newren via GitGitGadget
2020-07-28 20:45 ` [PATCH 1/2] Remove doubled words in various comments Elijah Newren via GitGitGadget
2020-07-28 20:45 ` [PATCH 2/2] hashmap: fix typo in usage docs Elijah Newren via GitGitGadget
2020-07-28 20:48 ` Taylor Blau [this message]
2020-07-28 21:27 ` [PATCH 0/2] Typo fixes 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=20200728204804.GA94132@syl.lan \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.