From: Andreas Enge <andreas@enge.fr>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] doc: Fix minor typos and add missing words.
Date: Tue, 23 Feb 2016 10:21:31 +0100 [thread overview]
Message-ID: <20160223092131.GA19268@solar> (raw)
In-Reply-To: <87vb5fooa2.fsf@gmail.com>
On Tue, Feb 23, 2016 at 10:53:57AM +0300, Alex Kost wrote:
> I would rather write: "The @code{(gnu services shepherd)} module ..."
> But I don't know if it's preferable or not, other opinions are needed.
> The rest fixes look good to me.
I will have a look at the documentation again next weekend (at the latest)
and can integrate this suggestion, as well as other pending ones.
Andreas
next prev parent reply other threads:[~2016-02-23 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 7:01 [PATCH] doc: Fix minor typos and add missing words Chris Marusich
2016-02-23 7:53 ` Alex Kost
2016-02-23 9:21 ` Andreas Enge [this message]
2016-02-24 20:35 ` Andreas Enge
2016-03-03 3:24 ` Chris Marusich
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=20160223092131.GA19268@solar \
--to=andreas@enge.fr \
--cc=alezost@gmail.com \
--cc=guix-devel@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).