From: Boqun Feng <boqun@kernel.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Open Meeting at Oct 15
Date: Tue, 3 Mar 2026 08:10:48 -0800 [thread overview]
Message-ID: <aacICOmj9E6XzYAS@tardis-2.local> (raw)
In-Reply-To: <aO0uLL8dZF6MuRib@tardis.local>
Hi all,
A little last-minute confirmation, but as usual, our Open Meeting will
be at Wednesday (Mar 4, 2026) 19:00 UTC and feel free to join via:
https://meet.google.com/cik-xrih-wij
Regards,
Boqun
prev parent reply other threads:[~2026-03-03 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 1:12 Rust for Linux Open Meeting Miguel Ojeda
2023-09-09 17:23 ` Boqun Feng
2023-11-06 18:52 ` No Open Meeting at Nov 15 Boqun Feng
2024-01-23 17:54 ` Open Meeting at Jan 24 Boqun Feng
2024-03-25 18:23 ` Open Meeting at March 27 Boqun Feng
2024-05-28 15:58 ` Open Meeting at May 29 Boqun Feng
2024-07-31 15:20 ` Open Meeting at Aug 7 Boqun Feng
2024-12-04 18:55 ` Open Meeting at Dec 11 Boqun Feng
2025-02-04 15:17 ` Open Meeting at Feb 5 Boqun Feng
2025-04-07 20:59 ` Open Meeting at April 16 Boqun Feng
2025-04-16 18:06 ` Boqun Feng
2025-06-08 17:40 ` Open Meeting at Jun 11 Boqun Feng
2025-08-12 15:56 ` Open Meeting at Aug 20 Boqun Feng
2025-10-13 16:51 ` Open Meeting at Oct 15 Boqun Feng
2026-03-03 16:10 ` Boqun Feng [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=aacICOmj9E6XzYAS@tardis-2.local \
--to=boqun@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=rust-for-linux@vger.kernel.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