ryan

it would be super great to have `net::IpAddr*` moved to core, it's a definite improvement, and it makes sense not to block on things that require more discussion... however, without...

hey @rust-lang/libs folks, sorry if this is already in the queue but, have y'all had a chance to look at this yet? i am on the edge of writing a...

hey thanks for your effort! seems like a fundamental crate so if @mbr (cc. @fpagliughi) are up for handing `socketcan` over it's a :+1: from me, any other opinions ~~@rust-embedded/tools~~...

in your initial `.cargo/config` it appears you're trying to build a rust `musl` target using a `gnu` linker, you need to use one or the other which should look like:...

[`[email protected]`](https://github.com/rust-embedded/embedded-hal/issues/177) :-/ though we -could- backport some of these changes to the `[email protected]` series if it was useful

it'd be super neat to have a way to run cargo release with protected `main` branches, which i think is basically the same scenario as this (though usually we'd manually...

ooh, interesting~! our usual release process uses [bors](https://bors.tech), so you create a release branch with the cargo version update, merge that, then publish from master (and tag anywhere along the...

Awesome! I just ran the same test for the silabs SVDs, and have just updated the repo with a pile more SVDs / automation to make adding further packages easier....

@japaric I have a bit of a mess going on but the latest copies of things are [here](https://github.com/ryankurte/rust-silabs/) (or SVDs [here](https://github.com/ryankurte/rust-silabs/tree/master/svd)) because I hadn't worked out whether / how to...

Have also been playing with @jameysharp's [share-svd](https://github.com/jameysharp/share-svd) also and [adapted it](https://github.com/ryankurte/share-svd/tree/cross-family-tests) to look across device families / output which peripherals are duplicated. Also in thinking about it more I realised...