git log --all --graph

I would have thought that you fix it locally, git commit, and regenerate the patch set again. Maybe with optional squashing of commits so each patch set doesn't keep growing.

I don't think the code is the problem they are cleaning up. I think they just want to remove the contributor from the history.

I mean it should. It'll have a steam os installed on the device itself. It'd be a pretty silly oversight to not work with a computer running Linux.

It is. Relatively so. This smells of Mozilla wanting to package things in there that Linux distro maintainers wouldn't package in themselves.

You may say I'm being overtly cynical and as much as I love Firefox, I can't say I trust Mozilla's intentions

Not so much toggled, but you can break out of it. At that point it just becomes a fedora install with a somewhat different set of defaults.

Nope. I make my code open source so the code is there in case someone finds it useful. I ain't supporting it outside of what I can be bothered to do though. It's open source, you chose to use it, it's on you to support yourself.

A bad company. Because they should be delivering a holistic product. But their hardware side knows their shit at least.

I think it's a script they added to do some sort of check with rustfmt.

Does GCC support pluggable backends? I feel when something like this comes up, the real answer should be, for those that make sense to drop from the core, it'd make sense to make them pluggable and separate them out, so that those that need them can pick them up if they need.

Can't libre office's calc work with Excel files?

Yeah. I had this problem. I ended up switching out the WiFi module for one with better Linux support. (In my laptop it's just a little m.2 thing).