From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Julien Lepiller <julien@lepiller.eu>, guix-devel@gnu.org
Subject: Re: Reworking the cookbook layout
Date: Wed, 27 Nov 2019 11:21:22 +0100 [thread overview]
Message-ID: <878so1livx.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20191126231136.212ff31e@sybil.lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 189 bytes --]
No strong opinion here, it seems to be a good idea.
My only current itch with the cookbook is that it might have too deep a
hierarchy.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-11-27 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 22:11 Reworking the cookbook layout Julien Lepiller
2019-11-27 10:21 ` Pierre Neidhardt [this message]
2019-11-27 14:21 ` sirgazil
2019-11-27 11:08 ` zimoun
2019-11-27 12:14 ` Julien Lepiller
2019-11-27 15:26 ` zimoun
2019-11-27 17:47 ` Julien Lepiller
2019-11-28 0:43 ` Bengt Richter
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=878so1livx.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).