You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've about outgrown the phase where I'm comfortable with people just pushing to the main repo to do test runs, and try pushes are one of the main reasons we have to give people write access via the 'Rust-Push' group. Let's move this functionality to it's own repo, and possibly even to it's own automation infrastructure.
The text was updated successfully, but these errors were encountered:
On Tue, Jun 17, 2014 at 11:55:40AM -0700, Brian Anderson wrote:
We've about outgrown the phase where I'm comfortable with people
just pushing to the main repo to do test runs, and try pushes are
one of the main reasons we have to give people write access via the
'Rust-Push' group. Let's move this functionality to it's own repo,
and possibly even to it's own automation infrastructure.
It would also be useful to have try runs test a superset of what bors
tests -- or at least have the option to do so.
Emit `'_` for lifetime generics in `HirDisplay`
This makes the generated code not linted by `rust_2018_idioms` lint. But that is an allow by default lint, so should we do this? Maybe we should only do this for `DisplayTarget::SourceCode`?
We've about outgrown the phase where I'm comfortable with people just pushing to the main repo to do test runs, and try pushes are one of the main reasons we have to give people write access via the 'Rust-Push' group. Let's move this functionality to it's own repo, and possibly even to it's own automation infrastructure.
The text was updated successfully, but these errors were encountered: