From: Fox <firefox@firemail.cc>
To: help-guix@gnu.org
Cc: guile-user@gnu.org
Subject: GNU Hackers Meeting, August 25 , 2017 in Germany (Kassel)
Date: Tue, 16 May 2017 21:30:58 +0200 [thread overview]
Message-ID: <offk1b$etj$2@blaine.gmane.org> (raw)
In-Reply-To: <8760h1cj2g.fsf@gnu.org>
dude, that ought to be one cool get-together! around 150 € if you can.
> Now’s the time to register for the GNU Hackers Meeting:
>
> https://www.gnu.org/ghm/
>
> https://lists.gnu.org/archive/html/ghm-discuss/2017-05/msg00000.html
>
> A bunch of Guix hackers (myself included) are planning to be there, so
> let’s take advantage of this event to meet in person, chat about all
> things Guix and GNU, and have a good time!
>
> It would be nice if you could propose a talk about how you use
> Guix{,SD}, your experience, or new use cases that you envision: Web
> service deployment, porting Guix{,SD} to new architectures,
> cross-compilation to {MinGW,aarch64,GNU/Hurd,PowerPC,alpha,whatnot},
> supporting multiple bootloaders, GuixSD service configuration & testing,
> HPC & scientific software, the Guix Worflow Language, channels &
> external package repos, the potluck, etc.
>
> Hoping to see you there!
>
> Ludo’
parent reply other threads:[~2017-05-16 19:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8760h1cj2g.fsf@gnu.org>]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='offk1b$etj$2@blaine.gmane.org' \
--to=firefox@firemail.cc \
--cc=guile-user@gnu.org \
--cc=help-guix@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.
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).