From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Next Dev Video Conf Call
Date: Sun, 26 Jun 2022 10:34:08 +0100 [thread overview]
Message-ID: <59810EFB-2017-4BF9-B3A9-532E0E85138B@ipfire.org> (raw)
In-Reply-To: <f9d3ae2b-d321-4842-e9f3-782aab77a4b8@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
I will be there :)
If you have any information for the group, please make sure to send it to the list before the conference.
Since we just had a call a little while ago, I don’t think there will be too much new stuff to talk about.
So enjoy your time off :)
-Michael
> On 25 Jun 2022, at 11:14, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> 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-26 9:34 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
2022-06-26 9:34 ` Michael Tremer [this message]
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=59810EFB-2017-4BF9-B3A9-532E0E85138B@ipfire.org \
--to=michael.tremer@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