Sjoerd Simons

What debian does or doesn't ship at the moment isn't that relevant ; Especially as we're in freeze going toward the next release some things are frozen at release that...

If this feature request seems reasonable i'd love to know if the draft PR is going in the right direction :) Though there is a good chunk of work there...

fwiw this should avoid panics like seen in https://github.com/k3s-io/k3s/issues/284#issuecomment-961262975

> While testing this PR, I realized that it breaks dual-stack. Nodes that have the correct config stop serving ipv6 addresses to pods and in the logs I can see...

> @manuelbuil from the comment > > > When moving nodes from single to dual-stack > > I suspect that what's going on here is: > > 1. Configure cluster...

For reference we've been running with this revert for Apertis for quite a while now and things seem entirely happy ;) But as @adalessandro mentioned we may well be missing...

fwiw the one thing we noticed recently that when publishing a distribution with a `/` "under" another distribution then removing the top-level one will remove everything underneath :) So that...

Actually no; The main bmap::copy should stay as generic as possible; Potentially the library crate could get some extra helper functions to deal with different/common outputs but that shouldn't be...

fwiw the first step to do for that is to make/keep the library crate build in a no_std environment; Which opens up the possibility to write a uefi app using...

Fwiw you can use the I2C interface directly by doing e.g. `I2CInterface::new(i2c, 03xc, 0x40)` rathe then going though the `I2CDisplayInterface` helper, avoiding the need to fork. Creating a Async version...