From: Catonano <catonano@gmail.com>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: guile-devel <guile-devel@gnu.org>,
guile-user <guile-user-bounces+amirouche=hypermove.net@gnu.org>,
Guix-devel <guix-devel@gnu.org>,
guile-user@gnu.org, Alex Sassmannshausen <alex@pompo.co>
Subject: Re: FOSDEM 2017 audio/video volunteers needed
Date: Wed, 11 Jan 2017 14:08:16 +0100 [thread overview]
Message-ID: <CAJ98PDwYcR9gLzOStrJbTxgvLAxre26oa7i_92B93NQezY=ZUA@mail.gmail.com> (raw)
In-Reply-To: <5a45d410288d7f6879ec9536133d7abc@hypermove.net>
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
2017-01-11 11:52 GMT+01:00 Amirouche Boubekki <amirouche@hypermove.net>:
>
> No response. We need help! Two people can take turns over the day.
>>> Please volunteer, it is important we capture all talks.
>>>
>>
>> I could do some of it, but I’m also giving talks, so we need at least
>> one more person to help out.
>>
>
> I hope I will be up to the task; count me in.
>
>
I can take a share of the burden. Count me in
[-- Attachment #2: Type: text/html, Size: 1059 bytes --]
next prev parent reply other threads:[~2017-01-11 13:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 22:47 FOSDEM 2017: GNU Guile & Guix call for talks! Ludovic Courtès
2016-11-07 16:58 ` Efraim Flashner
2016-11-08 2:23 ` Pjotr Prins
2016-12-18 15:26 ` FOSDEM 2017 Schedule is there! Pjotr Prins
2016-12-19 7:37 ` Alex Sassmannshausen
2017-01-03 14:46 ` FOSDEM 2017 Schedule is there! Change of schedule!:wq Pjotr Prins
2017-01-03 15:35 ` Amirouche Boubekki
2017-01-06 16:23 ` Pjotr Prins
2017-01-10 4:02 ` FOSDEM 2017 audio/video volunteers needed Pjotr Prins
2017-01-11 3:49 ` Pjotr Prins
2017-01-11 8:05 ` Ricardo Wurmus
2017-01-11 10:52 ` Amirouche Boubekki
2017-01-11 13:08 ` Catonano [this message]
2017-01-11 15:17 ` Pjotr Prins
2017-02-03 13:49 ` Catonano
2017-02-03 13:52 ` Thomas Danckaert
2017-02-06 11:44 ` FOSDEM 2017 what a success!! Pjotr Prins
2017-02-06 12:59 ` Ludovic Courtès
2017-02-07 21:32 ` Christopher Allan Webber
2017-02-03 14:00 ` FOSDEM 2017 audio/video volunteers needed Pjotr Prins
2017-02-04 12:42 ` Tobias Geerinckx-Rice
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='CAJ98PDwYcR9gLzOStrJbTxgvLAxre26oa7i_92B93NQezY=ZUA@mail.gmail.com' \
--to=catonano@gmail.com \
--cc=alex@pompo.co \
--cc=amirouche@hypermove.net \
--cc=guile-devel@gnu.org \
--cc=guile-user-bounces+amirouche=hypermove.net@gnu.org \
--cc=guile-user@gnu.org \
--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.
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).