From: "John Ericson" <list@johnericson.me>
To: rust-for-linux@vger.kernel.org
Subject: Re: [Rust for Linux] Happy new year & Poll for call
Date: Thu, 07 Jan 2021 20:22:56 -0500 [thread overview]
Message-ID: <79e121e9-a651-4dca-af50-1f82bee8aed5@www.fastmail.com> (raw)
In-Reply-To: <69c0082d-3505-4d65-889e-452a4ce3cea1@www.fastmail.com>
I'm sure you all actively working on this project will have more to say than me, but in the interest of keeping track of loose ends I made in the first place, I
- Posted https://internals.rust-lang.org/t/dogfooding-z-build-std-in-rustbuild/13775 about how -Z build-std could get more polish
- poked https://github.com/rust-lang/rust/pull/77916
Hope some of that is of interest,
John
On Thu, Jan 7, 2021, at 5:46 PM, John Ericson wrote:
> Sounds good, see you all there!
>
> On Thu, Jan 7, 2021, at 4:14 PM, Alex Gaynor wrote:
> > Thanks for organizing this Miguel!
> >
> > Alex
> >
> > On Thu, Jan 7, 2021 at 4:05 PM Miguel Ojeda
> > <miguel.ojeda.sandonis@gmail.com> wrote:
> > >
> > > On Sun, Jan 3, 2021 at 9:18 AM Miguel Ojeda
> > > <miguel.ojeda.sandonis@gmail.com> wrote:
> > > >
> > > > I propose next weekend Saturday 9th or Sunday 10th, at some point
> > > > between 16:00-21:00 UTC (EU evening / US afternoon).
> > >
> > > Thanks everyone for the replies! Let's do it Saturday 18:00 UTC then.
> > > Hopefully that is not that early for those in PST, just after lunch
> > > for EST and not too late for anywhere in Europe. :-)
> > >
> > > Cheers,
> > > Miguel
> >
> >
> >
> > --
> > All that is necessary for evil to succeed is for good people to do nothing.
> >
>
next prev parent reply other threads:[~2021-01-08 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 8:18 [Rust for Linux] Happy new year & Poll for call Miguel Ojeda
2021-01-07 21:03 ` Miguel Ojeda
2021-01-07 21:14 ` Alex Gaynor
2021-01-07 22:46 ` John Ericson
2021-01-08 1:22 ` John Ericson [this message]
2021-01-08 8:26 ` Miguel Ojeda
2021-01-08 14:34 ` John Ericson
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=79e121e9-a651-4dca-af50-1f82bee8aed5@www.fastmail.com \
--to=list@johnericson.me \
--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).