From: Ricardo Wurmus <rekado@elephly.net>
To: L p R n d n <guix@lprndn.info>
Cc: guix-devel@gnu.org
Subject: Re: Communication and Design at Guix
Date: Thu, 10 Jan 2019 15:30:13 +0100 [thread overview]
Message-ID: <87sgy04mbu.fsf@elephly.net> (raw)
In-Reply-To: <cucimywvfeu.fsf@lprndn.info>
L p R n d n <guix@lprndn.info> writes:
>> I’m not sure we need a wiki. :-)
>
> Yeah, I don't know. Still I think some things would benefit from
> not getting lost in the mailing list or IRC. :-/
If we have a bit of information that’s valuable enough to keep, it
should find its way into the manual. If there’s no suitable manual
section for that (e.g. one dedicated to examples) then it should be
added.
--
Ricardo
next prev parent reply other threads:[~2019-01-10 14:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:49 Communication and Design at Guix L p R n d n
2019-01-08 17:37 ` Ludovic Courtès
2019-01-09 6:11 ` swedebugia
2019-01-09 21:45 ` Ludovic Courtès
2019-01-10 12:09 ` L p R n d n
2019-01-10 13:20 ` swedebugia
2019-01-10 14:34 ` Ricardo Wurmus
2019-01-13 21:45 ` Ludovic Courtès
2019-01-14 15:02 ` L p R n d n
2019-01-15 10:36 ` zimoun
2019-01-15 18:03 ` nly
2019-01-15 22:08 ` Ricardo Wurmus
2019-01-16 11:00 ` Giovanni Biscuolo
2019-01-15 22:28 ` Ludovic Courtès
2019-01-14 23:25 ` swedebugia
2019-01-15 13:56 ` Ricardo Wurmus
2019-01-15 17:39 ` Julien Lepiller
2019-01-15 22:30 ` Ludovic Courtès
2019-01-10 12:17 ` L p R n d n
2019-01-10 12:57 ` L p R n d n
2019-01-10 14:30 ` Ricardo Wurmus [this message]
2019-01-13 21:50 ` Ludovic Courtès
2019-01-14 14:36 ` L p R n d n
2019-01-15 22:31 ` Ludovic Courtès
2019-01-16 16:31 ` George Clemmer
2019-01-17 0:10 ` swedebugia
2019-01-17 10:58 ` L p R n d n
2019-01-17 11:10 ` Ricardo Wurmus
2019-01-17 14:08 ` swedebugia
2019-01-17 16:24 ` L p R n d n
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgy04mbu.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=guix@lprndn.info \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.