All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Open Meeting at Oct 15
Date: Mon, 13 Oct 2025 09:51:56 -0700	[thread overview]
Message-ID: <aO0uLL8dZF6MuRib@tardis.local> (raw)
In-Reply-To: <aJtkNLp1pETbl9UI@Mac.home>

Hi all,

This is probably the last open meeting of this year because the next one
will likely be in Linux Plumbers/Christmas/New Year time. So feel free
to come to the open meeting at Wednesday (Oct 15, 2025) 18:00 UTC and
share what you have done and what you want to do in the next year in
Rust-for-Linux:

	https://meet.google.com/cik-xrih-wij

If you plan to present something cool, feel free to let us know
ahead of the time ;-)

Regards,
Boqun

  reply	other threads:[~2025-10-13 16:52 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                       ` Boqun Feng [this message]
2026-03-03 16:10                         ` Open Meeting at Oct 15 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=aO0uLL8dZF6MuRib@tardis.local \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.