From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Andrei Rybak" <rybak.a.v@gmail.com>,
git@vger.kernel.org, "Barret Rhoden" <brho@google.com>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
"Rafael Silva" <rafaeloliveira.cs@gmail.com>
Subject: Re: [PATCH v3 0/3] Config option names typofixes
Date: Sat, 26 Jun 2021 18:50:06 +0700 [thread overview]
Message-ID: <94a4dc6e-a8e7-d6d1-33c1-5a0dcfa9a4ca@gmail.com> (raw)
In-Reply-To: <20210625193851.2233114-1-rybak.a.v@gmail.com>
On 26/06/21 02.38, Andrei Rybak wrote:
> First patch in this series is the same as the v2 patch. Second patch fixes
> similar typos in mentions of config options in test messages. Third patch is
> just a fix for an unrelated typo I've stumbled upon.
>
> Andrei Rybak (3):
> blame: correct name of config option in docs
> t: fix typos in test messages
> git-worktree.txt: fix typo in example path
I suggest that the third patch should be on separate single patch, as it
is unrelated to two other patches that correct config option names.
Thanks.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2021-06-26 11:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 22:11 [PATCH] blame: fix typo in documentation Andrei Rybak
2021-06-19 5:27 ` Bagas Sanjaya
2021-06-19 11:12 ` Andrei Rybak
2021-06-19 11:20 ` Bagas Sanjaya
2021-06-19 17:31 ` Felipe Contreras
2021-06-19 11:29 ` [PATCH v2] blame: correct name of config option in docs Andrei Rybak
2021-06-20 9:37 ` Bagas Sanjaya
2021-06-21 16:57 ` Barret Rhoden
2021-06-25 19:38 ` [PATCH v3 0/3] Config option names typofixes Andrei Rybak
2021-06-25 19:38 ` [PATCH v3 1/3] blame: correct name of config option in docs Andrei Rybak
2021-06-25 19:38 ` [PATCH v3 2/3] t: fix typos in test messages Andrei Rybak
2021-06-25 19:38 ` [PATCH v3 3/3] git-worktree.txt: fix typo in example path Andrei Rybak
2021-06-26 6:58 ` Carlo Marcelo Arenas Belón
2021-06-26 10:07 ` Andrei Rybak
2021-06-29 1:12 ` Junio C Hamano
2021-06-26 11:50 ` Bagas Sanjaya [this message]
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=94a4dc6e-a8e7-d6d1-33c1-5a0dcfa9a4ca@gmail.com \
--to=bagasdotme@gmail.com \
--cc=brho@google.com \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=rafaeloliveira.cs@gmail.com \
--cc=rybak.a.v@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 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 NNTP newsgroup(s).