From: "Cook, Malcolm" <MEC@stowers.org>
To: "'Ludovic Courtès'" <ludo@gnu.org>,
"'Ricardo Wurmus'" <ricardo.wurmus@mdc-berlin.de>,
"'Pjotr Prins'" <pjotr2016@thebird.nl>,
"'Leo Famulari'" <leo@famulari.name>
Cc: 'Guix-devel' <guix-devel@gnu.org>,
"'bio-packaging@mailman.open-bio.org'"
<bio-packaging@mailman.open-bio.org>
Subject: RE: Making the case for GNU Guix ... advice sought
Date: Wed, 10 Feb 2016 16:01:30 +0000 [thread overview]
Message-ID: <a46c1c7f38bb498ab0cd5a211fabae84@exchsrv2.sgc.loc> (raw)
In-Reply-To: <87bn7psjss.fsf@gnu.org>
Hi,
Thanks everyone for the many valuable suggestions and education.
Next week I intend to incorporate the suggested improvements as best I can and follow up with an edit that I will use in-house, and share back out via git-hub.
Though the document is aimed at my particular internal "project justification", I am trying to keep it generic, and will welcome suggestions for further reshaping it to be of more general value should there be such interest from y'all.
GoGuix,
Malcolm
next prev parent reply other threads:[~2016-02-10 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 19:43 Making the case for GNU Guix ... advice sought Cook, Malcolm
2016-02-09 15:03 ` Ricardo Wurmus
2016-02-09 19:54 ` Leo Famulari
2016-02-09 20:27 ` Ludovic Courtès
2016-02-09 20:30 ` Ludovic Courtès
2016-02-18 23:29 ` Cook, Malcolm
2016-02-19 10:10 ` Pjotr Prins
2016-02-19 15:06 ` Cook, Malcolm
2016-02-28 13:52 ` Ludovic Courtès
2016-02-28 14:42 ` Ricardo Wurmus
2016-02-29 16:55 ` Cook, Malcolm
2016-02-29 17:10 ` Cook, Malcolm
2016-03-01 21:22 ` Ludovic Courtès
2016-02-09 20:36 ` Ludovic Courtès
2016-02-10 16:01 ` Cook, Malcolm [this message]
2016-02-18 23:26 ` Cook, Malcolm
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=a46c1c7f38bb498ab0cd5a211fabae84@exchsrv2.sgc.loc \
--to=mec@stowers.org \
--cc=bio-packaging@mailman.open-bio.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=ludo@gnu.org \
--cc=pjotr2016@thebird.nl \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.