From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Andrei Rybak <rybak.a.v@gmail.com>,
git@vger.kernel.org
Cc: Barret Rhoden <brho@google.com>
Subject: Re: [PATCH] blame: fix typo in documentation
Date: Sat, 19 Jun 2021 12:31:05 -0500 [thread overview]
Message-ID: <60ce29d9144e9_cc2b1208f8@natae.notmuch> (raw)
In-Reply-To: <8921ac50-e628-9a60-2a8d-1b8cc2a5a056@gmail.com>
Bagas Sanjaya wrote:
> That above is not typo fixing; that is correcting configuration variable
> name.
>
> PS: I have to download mbox of this thread and reply from it because I
> didn't receive the thread on my Thunderbird, regardless of CCing Git ML.
This is something I've noticed; I can always see mails on the archive,
however, I don't receive them on my inbox until much later.
--
Felipe Contreras
next prev parent reply other threads:[~2021-06-19 17:31 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 [this message]
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 ` [PATCH v3 0/3] Config option names typofixes Bagas Sanjaya
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=60ce29d9144e9_cc2b1208f8@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=brho@google.com \
--cc=git@vger.kernel.org \
--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.
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).