From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Missing conf call link
Date: Mon, 02 May 2022 18:55:42 +0100 [thread overview]
Message-ID: <4746056F-DF00-46D9-B3DA-6EA6A3F239B0@ipfire.org> (raw)
In-Reply-To: <e74a5229-81f9-7bfa-1827-ed69ed9b2cbf@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
There should be one now:
https://jitsi.ipfire.org/CloseGendersContinueAccurately
> On 2 May 2022, at 18:53, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
> There is no jitsi conf call link in the wiki conf call page for May 2nd.
>
> Adolf
>
> --
> Sent from my laptop
>
prev parent reply other threads:[~2022-05-02 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 17:53 Adolf Belka
2022-05-02 17:55 ` Michael Tremer [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=4746056F-DF00-46D9-B3DA-6EA6A3F239B0@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