From: Andreas Enge <andreas@enge.fr>
To: myglc2 <myglc2@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: FAQ
Date: Sat, 16 Jul 2016 19:18:34 +0200 [thread overview]
Message-ID: <20160716171834.GA15167@solar> (raw)
In-Reply-To: <cu7poqdh5xy.fsf@gmail.com>
On Sat, Jul 16, 2016 at 01:02:33PM -0400, myglc2 wrote:
> Vincent Legoll <vincent.legoll@gmail.com> writes:
> > OK, I'll try to create a FAQ section in the official doc then...
> Great idea!
Hm, lest I be misunderstood: The aim is that reading the manual should
be sufficient. If there is a frequently asked question, it should not
be added to an FAQ section, but the section of the documentation where
the question should be answered should be updated.
My reply was half meant as a joke. And half seriously: As a little joke
we could add an FAQ with only one question: "Where is the FAQ?" and the
answer "There is none, if you find the documentation is lacking, please
submit a patch to improve this manual." or the like.
Andreas
next prev parent reply other threads:[~2016-07-16 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 13:41 FAQ Vincent Legoll
2016-07-16 14:36 ` FAQ Andreas Enge
2016-07-16 14:52 ` FAQ Vincent Legoll
2016-07-16 17:02 ` FAQ myglc2
2016-07-16 17:18 ` Andreas Enge [this message]
2016-07-16 18:15 ` FAQ Alex Sassmannshausen
2016-07-16 19:58 ` FAQ Amirouche Boubekki
2016-07-16 18:19 ` FAQ Vincent Legoll
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=20160716171834.GA15167@solar \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=myglc2@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).