From: Linus Arver <linusa@google.com>
To: Eric Sunshine <sunshine@sunshineco.com>,
Linus Arver via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] docs: typofixes
Date: Wed, 07 Jun 2023 11:14:42 -0700 [thread overview]
Message-ID: <owlyr0qnnnql.fsf@fine.c.googlers.com> (raw)
In-Reply-To: <CAPig+cRE8=_WW_1_ER6=ObGaFzMdmQmESe5Gsb=dwo4DEx4u=A@mail.gmail.com>
Eric Sunshine <sunshine@sunshineco.com> writes:
> On Tue, Jun 6, 2023 at 8:56 PM Linus Arver via GitGitGadget
> <gitgitgadget@gmail.com> wrote:
>> These were found with an automated CLI tool [1]. Only the
>> "Documentation" subfolder (and not source code files) was considered
>> because the docs are user-facing.
>> [1]: https://crates.io/crates/typos-cli
>> Signed-off-by: Linus Arver <linusa@google.com>
>> ---
>> Documentation/CodingGuidelines | 2 +-
>> Documentation/config.txt | 2 +-
>> Documentation/git-cvsserver.txt | 2 +-
>> Documentation/git-describe.txt | 4 ++--
>> Documentation/git-format-patch.txt | 2 +-
>> Documentation/git-ls-tree.txt | 2 +-
>> Documentation/git-mktag.txt | 2 +-
>> Documentation/git-sparse-checkout.txt | 2 +-
>> Documentation/git-stash.txt | 2 +-
>> Documentation/gitweb.txt | 2 +-
>> Documentation/technical/remembering-renames.txt | 2 +-
>> Documentation/urls-remotes.txt | 2 +-
> These changes all look sensible. Thanks.
Thanks for the review --- but on second inspection I messed up the fix
to git-format-patch.txt. The tool suggested "interaction" which I
followed mechanically, but I noticed just now that the real fix should
have been "iteration". I have a v2 of this ready to got but GitGitGadget
is delayed due to GitHub experiencing an issue at the moment, so expect
some delay before the v2 gets pushed to the list.
next prev parent reply other threads:[~2023-06-07 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 0:51 [PATCH] docs: typofixes Linus Arver via GitGitGadget
2023-06-07 2:36 ` Eric Sunshine
2023-06-07 18:14 ` Linus Arver [this message]
2023-06-07 9:41 ` Kristoffer Haugsbakk
2023-06-07 17:09 ` Linus Arver
2023-06-07 19:26 ` [PATCH v2] " Linus Arver via GitGitGadget
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=owlyr0qnnnql.fsf@fine.c.googlers.com \
--to=linusa@google.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=sunshine@sunshineco.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).