From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: doc: Typos and small stylistic changes.
Date: Sun, 6 Mar 2016 14:10:42 +0100 [thread overview]
Message-ID: <20160306131042.GA13567@solar> (raw)
In-Reply-To: <877fhg38b2.fsf@gnu.org>
On Sat, Mar 05, 2016 at 10:48:33PM +0100, Ludovic Courtès wrote:
> This commit modifies some of the service documentation, which is also
> available in docstrings in gnu/services/*.scm. Could you update them
> accordingly?
Oh dear, correcting typos in the texinfo manual is already close to more
work than what the result is worth (but well, I am not complaining, I did it
voluntarily); now looking up where I marked my paper copy, checking how I
changed things in guix.texi and modifying the source code accordingly sounds
very tedious. I will give it a try.
I suppose it is not easily possible to import the doc strings automatically
into the texinfo file, in a way that we would keep a hand-written manual,
but with small pieces automatically extracted from the source code?
Maintaining two separate documents is always a bit painful.
Andreas
next prev parent reply other threads:[~2016-03-06 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160305152745.10002.35086@vcs.savannah.gnu.org>
[not found] ` <E1acE7O-0002cK-0Z@vcs.savannah.gnu.org>
2016-03-05 21:48 ` 01/01: doc: Typos and small stylistic changes Ludovic Courtès
2016-03-06 13:10 ` Andreas Enge [this message]
2016-03-06 13:46 ` Mathieu Lirzin
2016-03-06 15:26 ` Andreas Enge
2016-03-06 19:13 ` Mathieu Lirzin
2016-03-06 23:10 ` Ludovic Courtès
2016-03-06 16:02 ` Andreas Enge
2016-03-09 9:02 ` Alex Kost
2016-03-11 14:19 ` Ludovic Courtès
2016-03-14 19:58 ` Andreas Enge
2016-03-15 16:20 ` Ludovic Courtès
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=20160306131042.GA13567@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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).