all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Catonano <catonano@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>, myglc2 <myglc2@gmail.com>
Subject: Re: Guix infrastructure
Date: Tue, 11 Jul 2017 20:44:20 +0200	[thread overview]
Message-ID: <CAJ98PDzQO-wk1FeKjvMBvW8naDerL5AN76hoj4=GgnbdLW2iVQ@mail.gmail.com> (raw)
In-Reply-To: <87zicej8qr.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

Wow, I had totally missed this thread !

2017-07-09 10:49 GMT+02:00 Ricardo Wurmus <rekado@elephly.net>:

>
> myglc2 <myglc2@gmail.com> writes:
>
> > As you have experienced here, the learning/deployment costs and hassle
> > associated with each new type of server often dwarfs other costs. The
> > best way to minimize this is to minimize the number of types of servers
> > you own.
>
> The servers I’m preparing to add to the build farm once I’m back to the
> office are all of the same type.  There are dozens of them.
>

Ah, this is good news !

I can't wait :-)

[-- Attachment #2: Type: text/html, Size: 1055 bytes --]

  reply	other threads:[~2017-07-11 18:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01 17:36 stability of master - just QA and hydra is not enough ng0
2017-07-01 18:01 ` Leo Famulari
2017-07-01 19:24   ` ng0
2017-07-01 19:52     ` Leo Famulari
2017-07-07  0:09   ` myglc2
2017-07-07  3:00     ` Guix infrastructure Leo Famulari
2017-07-07 12:19       ` Ludovic Courtès
2017-07-08 23:50         ` ng0
2017-07-09  9:21           ` Ricardo Wurmus
2017-07-09 12:06             ` Liam Wigney
2017-07-09 22:57               ` ng0
2017-07-09  0:43         ` myglc2
2017-07-09  8:49           ` Ricardo Wurmus
2017-07-11 18:44             ` Catonano [this message]
2017-07-09  6:30       ` Efraim Flashner

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='CAJ98PDzQO-wk1FeKjvMBvW8naDerL5AN76hoj4=GgnbdLW2iVQ@mail.gmail.com' \
    --to=catonano@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=myglc2@gmail.com \
    --cc=rekado@elephly.net \
    /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.