From: Jeff King <peff@peff.net>
To: Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/3] Other doc fixes
Date: Tue, 5 Nov 2019 23:06:48 -0500 [thread overview]
Message-ID: <20191106040648.GC4307@sigill.intra.peff.net> (raw)
In-Reply-To: <pull.454.git.1572996692.gitgitgadget@gmail.com>
On Tue, Nov 05, 2019 at 11:31:29PM +0000, Elijah Newren via GitGitGadget wrote:
> In addition to the pile of spelling fixes in my other pull request, here are
> some simple documentation fixes other than spelling errors (remove repeated
> word, '.' vs '->', missing hyphen).
Thanks, these all look trivially correct to me.
-Peff
prev parent reply other threads:[~2019-11-06 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 23:31 [PATCH 0/3] Other doc fixes Elijah Newren via GitGitGadget
2019-11-05 23:31 ` [PATCH 1/3] git-filter-branch.txt: correct argument name typo Elijah Newren via GitGitGadget
2019-11-05 23:31 ` [PATCH 2/3] hashmap: fix documentation misuses of -> versus Elijah Newren via GitGitGadget
2019-11-05 23:31 ` [PATCH 3/3] name-hash.c: remove duplicate word in comment Elijah Newren via GitGitGadget
2019-11-07 5:41 ` Junio C Hamano
2019-11-06 4:06 ` Jeff King [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=20191106040648.GC4307@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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).