From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Pjotr Prins <pjotr.public12@thebird.nl>,
Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Subject: Re: FOSDEM 2016 was awesome! Let's do FOSDEM 2017
Date: Tue, 26 Jul 2016 12:33:01 +0200 [thread overview]
Message-ID: <2b4c4b46-db73-657b-6787-47acf10c0848@tobias.gr> (raw)
In-Reply-To: <20160726021928.GA28372@thebird.nl>
Pjotr,
On 26/07/2016 4:19, Pjotr Prins wrote:
> FOSDEM 2017 call for proposals has started: [...]
> Who wants to be part of this exciting day?
\o
I've never done anything like this before, but would like to help out if
and where I can.
Kind regards,
T G-R
next prev parent reply other threads:[~2016-07-26 10:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 2:19 FOSDEM 2016 was awesome! Let's do FOSDEM 2017 Pjotr Prins
2016-07-26 10:33 ` Tobias Geerinckx-Rice [this message]
2016-07-26 11:25 ` Manolis Ragkousis
2016-08-04 16:58 ` Christopher Allan Webber
2016-08-04 20:35 ` Ludovic Courtès
2016-08-05 21:12 ` Amirouche Boubekki
2016-08-26 7:12 ` FOSDEM 2016 was awesome! Let's do FOSDEM 2017 - add talk proposals Pjotr Prins
2016-08-29 7:37 ` FOSDEM 2016 was awesome! Let's do FOSDEM 2017 Alex Sassmannshausen
2016-08-30 8:19 ` Pjotr Prins
2016-08-30 8:28 ` Alex Sassmannshausen
2016-10-05 14:09 ` FOSDEM 2016 was awesome! Let's do FOSDEM 2017 (we are IN!) Pjotr Prins
2016-10-05 15:17 ` Alex Sassmannshausen
2016-10-05 16:52 ` Ludovic Courtès
2016-10-06 12:41 ` Amirouche Boubekki
2016-10-18 9:00 ` FOSDEM 2017: GNU Guile/Guix call for talks! Pjotr Prins
2016-11-20 16:35 ` FOSDEM 2016 was awesome! Let's do FOSDEM 2017 Leo Famulari
2016-11-21 19:04 ` Efraim Flashner
2016-11-23 21:19 ` Ludovic Courtès
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=2b4c4b46-db73-657b-6787-47acf10c0848@tobias.gr \
--to=me@tobias.gr \
--cc=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=pjotr.public12@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.