unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: comment about GuixSD on freepo.st
Date: Thu, 14 Jul 2016 16:12:57 -0400	[thread overview]
Message-ID: <20160714201257.GB32471@jasmine> (raw)
In-Reply-To: <87poqgqt1l.fsf@we.make.ritual.n0.is>

On Thu, Jul 14, 2016 at 12:54:14PM +0000, ng0 wrote:
> I commented on an older (1 year) post about GuixSD, while what I
> wrote looks accurate to me, does someone spot any mistakes (like
> misspelled names etc)?

I think it looks good :)

For the last question, I think that this paper explains the motivation
pretty well:
https://hal.inria.fr/hal-00824004/en

  reply	other threads:[~2016-07-14 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 12:54 comment about GuixSD on freepo.st ng0
2016-07-14 20:12 ` Leo Famulari [this message]
2016-07-14 23:12   ` ng0

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=20160714201257.GB32471@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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).