From: ludo@gnu.org (Ludovic Courtès)
To: myglc2 <myglc2@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>, Pjotr Prins <pjotr2017@thebird.nl>
Subject: Re: Let’s meet before FOSDEM!
Date: Tue, 07 Nov 2017 23:50:38 +0100 [thread overview]
Message-ID: <87vailwvnl.fsf@gnu.org> (raw)
In-Reply-To: <86lgjitadp.fsf@gmail.com> (myglc2@gmail.com's message of "Tue, 07 Nov 2017 09:46:10 -0500")
myglc2 <myglc2@gmail.com> skribis:
> I am thinking of coming from Boston on the cheap to finally put a face
> on all you helpful Guixers, and maybe go to FOSDEM.
>
> My personal interests are HPC, reproducible research, Cuirass, and
> "user-level" use of git pull instead of guix pull.
Cool!
> Are you saying there will be no Guix discussion at FOSDEM?
There will be no “developer room” akin to what we had for the last
couple of years¹ (we had a Guile/Guix track at FOSDEM for half a day and
then for a whole day, which was awesome.) Hopefully there’ll be a
couple of Guix talks in other tracks though.
Ludo’.
¹ https://lists.gnu.org/archive/html/guix-devel/2017-10/msg00061.html
next prev parent reply other threads:[~2017-11-07 22:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 13:39 Let’s meet before FOSDEM! Ludovic Courtès
2017-11-07 14:14 ` ng0
2017-11-07 14:19 ` julien lepiller
2017-11-07 14:46 ` myglc2
2017-11-07 22:50 ` Ludovic Courtès [this message]
2017-11-07 17:00 ` Pjotr Prins
2017-11-07 18:09 ` Jan Nieuwenhuizen
2017-11-07 18:23 ` Ricardo Wurmus
2017-11-07 19:06 ` Roel Janssen
2017-11-07 19:18 ` Marius Bakke
2017-11-07 21:49 ` Pjotr Prins
2017-11-08 8:49 ` Ludovic Courtès
2018-01-06 17:16 ` Catonano
2017-11-08 7:57 ` Christopher Baines
2017-11-08 10:23 ` Efraim Flashner
2017-11-08 12:20 ` benjaminsutter
2017-11-08 13:57 ` Ludovic Courtès
2017-11-08 22:51 ` ng0
2017-11-09 15:45 ` Pjotr Prins
2018-01-20 14:16 ` Danny Milosavljevic
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=87vailwvnl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
--cc=pjotr2017@thebird.nl \
/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.