From: N <ng0@n0.is>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Will August 16-18, Berlin actually happen?
Date: Sat, 3 Aug 2019 07:45:54 +0000 [thread overview]
Message-ID: <20190803074554.soh62jhl5iz5lpyi@uptimegirl> (raw)
In-Reply-To: <87tvb094dk.fsf@sdf.lonestar.org>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Jakob L. Kreuze transcribed 1.7K bytes:
> Hi Hartmut,
>
> Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
>
> > Hi,
> >
> > I consider traveling to the August 16-18 Meeting in Berlin.
> > https://md.darmstadt.ccc.de/gnunet-events# state this will "happen",
> > but the announcements sounds more like "planning" for me. (Also I
> > would need to fill the gap from Sunday to Wednesday, when cccamp
> > starts, which is a bit unfortunate.)
> >
> > Will this meeting actually happen? Is there some kind of agenda
> > already? Who//How many will attend?
>
> This is my first time hearing of this event, so I'm afraid I can't
> answer any of your questions. Coincidentally, I will be in Berlin those
> three days, so please let me know if you hear back -- I'm interested in
> attending.
>
> (On that note, who is sva? Perhaps I should sign up.)
>
> Regards,
> Jakob
It is more of an internal, not public event but you can ask regardless of
this, worst case sva or someone else says no.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-03 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 16:00 Will August 16-18, Berlin actually happen? Hartmut Goebel
2019-08-01 17:34 ` Jakob L. Kreuze
2019-08-03 7:45 ` N [this message]
2019-08-03 17:06 ` Jakob L. Kreuze
2019-08-01 17:49 ` Tobias Geerinckx-Rice
[not found] <e25f61e6-e93b-af1b-a62a-7abe6a79ed5d@crazy-compilers.com>
2019-08-01 17:46 ` Hartmut Goebel
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=20190803074554.soh62jhl5iz5lpyi@uptimegirl \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=zerodaysfordays@sdf.lonestar.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.