rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Stappers <stappers@stappers.nl>
To: rust-for-linux@vger.kernel.org
Subject: Re: [Rust for Linux] Poll for call
Date: Thu, 18 Mar 2021 21:58:33 +0100	[thread overview]
Message-ID: <20210318205833.vshwyokm3ahogjrw@gpm.stappers.nl> (raw)
In-Reply-To: <CAFRnB2WSVcPyH4Wvp9SWP8O=L8ZjEKhXf0=oXPj9h2XHT1yh7Q@mail.gmail.com>


On Tue, Mar 16, 2021 at 12:57:53PM -0400, Alex Gaynor wrote:
> On Tue, Mar 16, 2021 at 12:40 PM Miguel Ojeda wrote:
> >
> > Hi all,
> >
> > As discussed in the previous meeting, let's have one meeting focused
> > on having a re-review of the code for the RFC.

Not sure what kind of a meeting, but my intention is to attent
and just listen.  Hear what real programmers talk about.


> > We have a fair amount of new code coming in and I am preparing a few
> > things too, but it should still be fine by the original schedule [1],
> > so I propose Saturday 27th or Sunday 28th at 18:00 UTC like last time
> > (EU evening / US afternoon).
> >
> > If all goes well, we should be able to send the RFC soon after -rc5.
> 
> I will hopefully be able to make that -- the 27th is unusually busy
> for a pandemic day for me :-)


Both 2021-03-27 [2]  and 2021-03-28 are fine for me.


Regards
Geert Stappers

[1] https://lore.kernel.org/rust-for-linux/CANiq72knSgMU30A2ALaJGY5FWumPKU18ThvfjR1t14_77kYLrQ@mail.gmail.com/
[2] https://xkcd.com/1179/  Oops 2013-02-27  was in Februari eight years ago
-- 
Silence is hard to parse

  reply	other threads:[~2021-03-18 20:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 15:14 [Rust for Linux] Poll for call Miguel Ojeda
2021-03-16 16:57 ` Alex Gaynor
2021-03-18 20:58   ` Geert Stappers [this message]
2021-03-24 12:41 ` Miguel Ojeda
2021-03-24 21:12   ` [Rust for Linux] Call Sunday 2021-03-28 18:00 UTC Geert Stappers
2021-03-25  8:16     ` Miguel Ojeda
2021-03-25  9:02       ` Kaviraj Kanagaraj
2021-03-25  9:25         ` Miguel Ojeda
2021-03-27 11:49           ` Geert Stappers
2021-03-28 13:23             ` Miguel Ojeda
2021-03-28 20:20               ` Miguel Ojeda
2021-03-28 20:42                 ` Kaviraj Kanagaraj
2021-03-27 15:27       ` Joshua Abraham
  -- strict thread matches above, loose matches on Subject: below --
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
     [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

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=20210318205833.vshwyokm3ahogjrw@gpm.stappers.nl \
    --to=stappers@stappers.nl \
    --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).