From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Chen, Hongzhan" <hongzhan.chen@intel.com>,
Richard Weinberger <richard.weinberger@gmail.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: Reminder: Xenomai community call on Wednesday, Sep 20, 2023, UTC 7:00 AM
Date: Tue, 10 Oct 2023 06:25:59 +0200 [thread overview]
Message-ID: <7c71c982-a3a8-447b-8d1b-2f01cb506759@siemens.com> (raw)
In-Reply-To: <MN2PR11MB42853939B9B762880D88439AF2CDA@MN2PR11MB4285.namprd11.prod.outlook.com>
On 10.10.23 02:36, Chen, Hongzhan wrote:
>
>
>> -----Original Message-----
>> From: Richard Weinberger <richard.weinberger@gmail.com>
>> Sent: Wednesday, October 4, 2023 2:54 PM
>> To: Chen, Hongzhan <hongzhan.chen@intel.com>
>> Cc: xenomai@lists.linux.dev
>> Subject: Re: Reminder: Xenomai community call on Wednesday, Sep 20, 2023,
>> UTC 7:00 AM
>>
>> On Wed, Sep 20, 2023 at 4:17 AM Chen, Hongzhan
>> <hongzhan.chen@intel.com> wrote:
>>>
>>> We have the Xenomai community call today.
>>
>> I'm lost. What is the current community call cycle? Shouldn't be one today?
>
> Sorry, I notified you via email address Richard Weinberger <richard@nod.at> about the meeting cancel.
> I would notify you via email address richard.weinberger@gmail.com next time.
>
Go via the mailing list, just like you do for the reminders. Then you
don't need to worry about individual addresses.
Jan
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2023-10-10 4:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 2:17 Reminder: Xenomai community call on Wednesday, Sep 20, 2023, UTC 7:00 AM Chen, Hongzhan
2023-10-04 6:53 ` Richard Weinberger
2023-10-04 8:21 ` Jan Kiszka
2023-10-10 0:36 ` Chen, Hongzhan
2023-10-10 4:25 ` Jan Kiszka [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=7c71c982-a3a8-447b-8d1b-2f01cb506759@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=hongzhan.chen@intel.com \
--cc=richard.weinberger@gmail.com \
--cc=xenomai@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).