From: Jack Hill <jackhill@jackhill.us>
To: 39681@debbugs.gnu.org
Subject: bug#39681: Manual typo in section "Invoking ‘guix time-machine’"
Date: Wed, 19 Feb 2020 17:10:36 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.2002191705060.11123@marsh.hcoop.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
Tags: easy
Hello Guix,
In the manual section 4.8, "Invoking ‘guix time-machine’", I believe that
"are passed unmodified to the ‘guix’ command if the specified revision,"
would read better if it said, "to the ‘guix’ command of the specified
revision."
I've filed this as a bug like #39417 as an easy task for Outreachy
applicants. Let me know if a patch would be preferred.
Best,
Jack
next reply other threads:[~2020-02-19 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 22:10 Jack Hill [this message]
2020-03-24 5:31 ` bug#39681: [Outreachy] Submitting Patch for : Manual typo in section "Invoking ‘guix time-machine’" Naga Malleswari
2020-03-24 12:08 ` Danny Milosavljevic
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=alpine.DEB.2.20.2002191705060.11123@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=39681@debbugs.gnu.org \
/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).