From: Josh Triplett <josh@joshtriplett.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Technical call on `alloc`
Date: Thu, 10 Jun 2021 12:20:47 -0700 [thread overview]
Message-ID: <YMJmD6PGJlKC9DWH@localhost> (raw)
In-Reply-To: <CANiq72kZPOgK7NRkmfpbaks365s-9VcYN4N0Trwb0c+2xBzYdA@mail.gmail.com>
On Thu, Jun 10, 2021 at 05:22:56PM +0200, Miguel Ojeda wrote:
> On Thu, Jun 10, 2021 at 5:20 PM Miguel Ojeda
> <miguel.ojeda.sandonis@gmail.com> wrote:
> >
> > The two best options seem to be both 15:00 UTC, so I have picked the
> > Monday one to have Alex with us. Fox, Josh, Douglas: sorry!
>
> Sorry, I meant 13:00 UTC (15:00 CET).
Despite the early time, I'll try to join. :)
prev parent reply other threads:[~2021-06-10 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 9:43 Technical call on `alloc` Miguel Ojeda
2021-06-10 15:20 ` Miguel Ojeda
2021-06-10 15:22 ` Miguel Ojeda
2021-06-10 19:20 ` Josh Triplett [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=YMJmD6PGJlKC9DWH@localhost \
--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).