From: Carsten Strotmann <cas@strotmann.de>
To: linux-m68k <linux-m68k@lists.linux-m68k.org>,
Debian-68k <debian-68k@lists.debian.org>
Subject: virtual eventing chat meeting today
Date: Fri, 10 Jul 2020 10:18:48 +0200 [thread overview]
Message-ID: <86zh87236f.fsf@emacs.strotmann.de> (raw)
In-Reply-To: <86sgeskyb7.fsf@emacs.strotmann.de>
Hi,
a short reminder of the next virtual eventing chat meeting will be
on
10th of July 2020 (today) starting at 8:00pm CEST (20:00 H) on
<https://meet.m68k.info> (the Jitsi meeting page will be online 30
minutes before the meeting starts.
Based on the discussion last month I've created a prototype of an
"planet m68k" news aggregator website (that could also be used as
a
source for a monthly newsletter) containing m68k development news.
Also, the poll for a larger m68k developers meeting in Q4/2020 is
still
open (and will be open until end of August)
<https://nuudel.digitalcourage.de/sBwNfnUh2BjGWHJY>
See you tonight
Carsten
next prev parent reply other threads:[~2020-07-10 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 18:45 Virtual m68k Developer Meeting 2020 Carsten Strotmann
2020-07-10 8:18 ` Carsten Strotmann [this message]
2020-07-10 8:26 ` virtual eventing chat meeting today John Paul Adrian Glaubitz
2020-07-10 17:35 ` Carsten Strotmann
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=86zh87236f.fsf@emacs.strotmann.de \
--to=cas@strotmann.de \
--cc=debian-68k@lists.debian.org \
--cc=linux-m68k@lists.linux-m68k.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