From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 58564@debbugs.gnu.org
Subject: [bug#58564] [PATCH] gnu: Fix typos.
Date: Sun, 16 Oct 2022 12:58:48 +0200 [thread overview]
Message-ID: <87tu44uj6j.fsf@nckx> (raw)
In-Reply-To: <20221016125053.2c4a14c1@sybil.lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 233 bytes --]
Hi Julien,
I noticed another typo. This should be:
- "Setup @command{gitolite}, a Git hosting tool providing
access over SSH..
+ "Set up @command{gitolite}, a Git hosting tool providing
access over SSH.
LGTM!
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-10-16 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 10:50 [bug#58564] [PATCH] gnu: Fix typos Julien Lepiller
2022-10-16 10:58 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-10-17 5:34 ` bug#58564: " Julien Lepiller
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu44uj6j.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=58564@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=me@tobias.gr \
/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://git.savannah.gnu.org/cgit/guix.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).