From: Boqun Feng <boqun.feng@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: No Open Meeting at Nov 15
Date: Mon, 6 Nov 2023 10:52:19 -0800 [thread overview]
Message-ID: <ZUk14802ZWGpR2iM@boqun-archlinux> (raw)
In-Reply-To: <ZPyqLJ62B2GZg6BA@boqun-archlinux>
On Sat, Sep 09, 2023 at 10:23:56AM -0700, Boqun Feng wrote:
> On Tue, Jul 11, 2023 at 03:12:15AM +0200, Miguel Ojeda wrote:
> > Hi all,
> >
> > We will have our Open Meeting call on Wednesday 18:00 UTC (first
> > Wednesday after -rc1 is tagged).
> >
> > https://meet.google.com/vii-meij-xpw
> >
> > Like in the case of our old informal call, everybody is welcome to join.
> >
>
> Just a reminder, same as the previous one, we will have the "Open
> Meeting" call on Sep 13 18:00 UTC, come and join us ;-)
>
Since the next rc1 week is also LPC week, and most of folks will be
attending LPC, so let's cancel the meeting at Nov 15.
If you attend LPC, feel free to come and say hi ;-)
Regards,
Boqun
next prev parent reply other threads:[~2023-11-06 18:53 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 ` Boqun Feng [this message]
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
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=ZUk14802ZWGpR2iM@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=miguel.ojeda.sandonis@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