From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Let's skip Novembers call
Date: Fri, 27 Oct 2023 11:35:31 +0200 [thread overview]
Message-ID: <480d88f3-d101-40d1-bf94-b687d6af5d02@ipfire.org> (raw)
In-Reply-To: <79BBE990-6678-4632-90DA-DC3DDEC4685B@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
I can work with that.
No problems.
Regards,
Adolf.
On 26/10/2023 17:17, Michael Tremer wrote:
> Hello everyone,
>
> We already briefly talked about this at the end of this months call, that a lot of people are unavailable for next month’s call. It also happens that our usual strategy of moving it to the following Monday does not work, because a couple of people have said that that date does not work for them either.
>
> So, in order to not complicate things any further, let’s skip the November call and either move anything that cannot wait until the next one to the list, or have people arrange a call for an individual topic.
>
> Let me know if this all works for you.
>
> All the best,
> -Michael
--
Sent from my laptop
prev parent reply other threads:[~2023-10-27 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 15:17 Michael Tremer
2023-10-27 9:35 ` Adolf Belka [this message]
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=480d88f3-d101-40d1-bf94-b687d6af5d02@ipfire.org \
--to=adolf.belka@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