From: Josh Triplett <josh@joshtriplett.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
rust-for-linux@vger.kernel.org
Subject: Re: [Rust for Linux] Poll for call
Date: Fri, 05 Mar 2021 09:25:02 -0800 [thread overview]
Message-ID: <03864FA7-25E8-45DE-AF60-6B82B7C33588@joshtriplett.org> (raw)
In-Reply-To: <CANiq72njjy7sJ=_mgjKNzaHcwRgoWkQmgSN2Fq6gdCYoeD1WZg@mail.gmail.com>
On March 3, 2021 2:26:15 AM PST, Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
>Hi all,
>
>It has been about 2 months since the last call. We have a few bits to
>discuss regarding upstreaming, so I think it is a good time to have
>another informal call.
>
>Like last time, you are welcome to join even if you have been busy
>lately but still want to follow development. So don't worry about
>getting up to speed -- I'll give a quick briefing if needed.
>
>I propose next weekend Saturday 6th or Sunday 7th at 18:00 UTC like
>last time (EU evening / US afternoon).
>
>Please let me know which day you prefer, if any, and feel free to
>Cc/invite whoever you want!
>
>Cheers,
>Miguel
Either works for me.
next prev parent reply other threads:[~2021-03-05 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 10:26 [Rust for Linux] Poll for call Miguel Ojeda
2021-03-04 17:41 ` Nick Desaulniers
2021-03-05 16:00 ` Wedson Almeida Filho
2021-03-05 16:57 ` Adam Bratschi-Kaye
[not found] ` <CACAkLurwvSnV-5VuY1=Pocaw0VW-Axv=DgmU83v1NP=+a6ExAA@mail.gmail.com>
2021-03-05 12:00 ` Miguel Ojeda
2021-03-06 14:16 ` Sumera Priyadarsini
2021-03-05 17:25 ` Josh Triplett [this message]
[not found] ` <B1F9C55A-AA3D-418C-8C2C-BB1EE794D5D1@kloenk.dev>
2021-03-06 9:15 ` Miguel Ojeda
2021-03-06 9:23 ` Finn Behrens
2021-03-06 9:32 ` Miguel Ojeda
2021-03-16 15:14 Miguel Ojeda
2021-03-16 16:57 ` Alex Gaynor
2021-03-18 20:58 ` Geert Stappers
2021-03-24 12:41 ` Miguel Ojeda
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=03864FA7-25E8-45DE-AF60-6B82B7C33588@joshtriplett.org \
--to=josh@joshtriplett.org \
--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;
as well as URLs for NNTP newsgroup(s).