all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Building a software toolchain that works
Date: Thu, 17 Mar 2022 13:06:26 +0100	[thread overview]
Message-ID: <87h77w941p.fsf@gmail.com> (raw)
In-Reply-To: g7jNNhg5OJCBmXfXsEg3rtuHIKu2oesfKHMY9o2fqG9laMzAPYdjnYzSSakKf5NjikIUT_dTd5--XEHqTYv_8QZlY7W4qjqVFyc1I7dntD8=@protonmail.com

Hi Ryan,

> a. My Guile isn't strong enough to put together a proof-of-concept in
> Guix as a solo effort. I might be able to write a PoC in concert with
> a more experienced Guiler. We could schedule some strategy & pair
> programming sessions to get something on track.

Do not miss:

<https://rednosehacker.com/how-to-setup-a-remote-pair-programming-environment-with-gnu-guix>

Hope that helps,
simon


             reply	other threads:[~2022-03-17 13:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 12:06 zimoun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-14 19:05 Building a software toolchain that works Ryan Prior
2022-03-14 20:26 ` Pjotr Prins
2022-03-14 21:40   ` David Arroyo
2022-03-15  8:19     ` Ludovic Courtès
2022-03-17  9:20       ` zimoun
2022-03-16 14:02     ` Josselin Poiret
2022-03-16 15:28       ` Ryan Prior
2022-03-16 20:13         ` Yasuaki Kudo
2022-03-17 15:35     ` Maxime Devos
2022-03-17 16:56       ` David Arroyo
2022-03-14 23:57   ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-03-15  8:23     ` Ludovic Courtès
2022-03-15  8:42       ` Pjotr Prins
2022-03-15 12:32       ` Yasuaki Kudo
2022-03-17 12:56     ` zimoun
2022-03-18 21:13       ` david larsson
2022-03-18 23:59         ` Yasuaki Kudo
2022-03-17 20:04   ` Katherine Cox-Buday
2022-03-18  6:27     ` Pjotr Prins
2022-03-18  9:10       ` Oliver Propst

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=87h77w941p.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    /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.