From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Next Dev Video Conf Call
Date: Sat, 25 Jun 2022 10:14:15 +0000 [thread overview]
Message-ID: <f9d3ae2b-d321-4842-e9f3-782aab77a4b8@ipfire.org> (raw)
In-Reply-To: <c7696950-2638-9303-5297-4d7be29e6e72@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
Hello development folks,
on this occasion, again the note that I also won't be able to join next week.
Aside from Core Update 169, 170, and the usual batch of exciting news from the
IPFire 3.x ecosphere, I have nothing for the agenda. Will populate the Wiki
page, but feel free to change or skip these points, if necessary.
Thanks, and best regards,
Peter Müller
next prev parent reply other threads:[~2022-06-25 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:26 Adolf Belka
2022-06-25 10:14 ` Peter Müller [this message]
2022-06-26 9:34 ` Michael Tremer
2022-06-26 16:54 ` Daniel Weismüller
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=f9d3ae2b-d321-4842-e9f3-782aab77a4b8@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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