unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: New blog post on the Guix Build Coordinator: Building derivations, how complicated can it be?
Date: Sat, 24 Apr 2021 11:21:49 +0200	[thread overview]
Message-ID: <CAEwRq=qtsnzd-sOjdvopSvqbnuaN4sNtMjf=REP1pZsYKSrP8Q@mail.gmail.com> (raw)
In-Reply-To: <8735vggi91.fsf@cbaines.net>

On Sat, Apr 24, 2021 at 11:10 AM Christopher Baines <mail@cbaines.net> wrote:
> I did think about trying to include something about Cuirass, but I don't
> have a clear picture of it's scope or purpose, so I'm not really the
> right person to attempt to write authoritatively about it.

OK, fair enough, Matthieu, Ludo, or anyone else can shed some light
here ?

> I try to avoid using the CI (Continuous Integration) term as I'm not
> sure there's a shared understanding of the term (I think it's the
> practice of multiple people frequently merging their changes to some
> software they're all working on).

Yes, I know the term is overloaded, but it's easy and conveys at least
a bit of the subject at hands, so...

> Does that make any sense? Do say if you have more questions.

Yes, and I will, thanks

-- 
Vincent Legoll


  reply	other threads:[~2021-04-24  9:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24  6:28 New blog post on the Guix Build Coordinator: Building derivations, how complicated can it be? Christopher Baines
2021-04-24  8:19 ` Vincent Legoll
2021-04-24  9:10   ` Christopher Baines
2021-04-24  9:21     ` Vincent Legoll [this message]
2021-04-25 10:17       ` Mathieu Othacehe
2021-04-30 14:48         ` Ludovic Courtès
2021-04-30 20:59           ` Vincent Legoll

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='CAEwRq=qtsnzd-sOjdvopSvqbnuaN4sNtMjf=REP1pZsYKSrP8Q@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.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 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).