From: "Christian T. Steigies" <cts@debian.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Debian m68k <debian-68k@lists.debian.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Debian 68k meeting in 2018
Date: Thu, 9 Nov 2017 10:57:38 +0100 [thread overview]
Message-ID: <20171109095738.GA22602@nunzio.venus.sol> (raw)
In-Reply-To: <d01ce7aa-a134-56de-fc4c-3079cd544465@physik.fu-berlin.de>
Moin,
On Wed, Nov 08, 2017 at 02:11:15PM +0100, John Paul Adrian Glaubitz wrote:
>
> Can you suggest some dates? I assume, we do it on a weekend again.
Well, next year is special, there are more than 50 weekends! Do you want me
to list them all and block rooms already? Maybe we can limit the timeframe a
little bit. Do you want a meeting in Winter like last time? Should be easy
to get (meeting and hotel) rooms here, since it will be dark and miserable.
The FOSDEM weekend is probably not a good choice, so January? Really?
Lectures will be over on Feb 14, exams on Feb 21. After that until April the
University should be mostly empty, but I might be away for a week or two.
The first half of March looks good right now, the sun is coming back, so we
could go swimming, the baltic usually does not freeze anymore in March ;-)
If you want it later in the year, I would suggest late August / early
September, like last time. It will be hot (20°C!) and sunny, no classes.
But there I'd need to check for other conferences here first, this is the
preferred time for meetings.
Probably you want some feedback from Geert and Michael and Roman and
Thorsten and Andreas and Ingo and ... first before we lockin a date?
Christian
next prev parent reply other threads:[~2017-11-09 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 11:51 Debian 68k meeting in 2018 John Paul Adrian Glaubitz
2017-11-08 12:08 ` Christian T. Steigies
2017-11-08 12:23 ` ALeX Kazik
2017-11-08 13:11 ` John Paul Adrian Glaubitz
2017-11-09 9:57 ` Christian T. Steigies [this message]
2017-11-09 10:03 ` John Paul Adrian Glaubitz
2017-11-09 11:17 ` Carsten Strotmann
2017-11-13 19:05 ` Ingo Jürgensmann
2017-11-09 10:07 ` Ingo Jürgensmann
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=20171109095738.GA22602@nunzio.venus.sol \
--to=cts@debian.org \
--cc=debian-68k@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.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