Peter Barker

> My pre-commit environment is hosed, feel free to merge based on other approvals. This does not fill me with confidence. tridge also ended up with a "hosed" pre-commit environment....

Merged, thanks!

Just thought I'd mention my workflow for using modified message definitions. ``` pbarker@fx:~/rc/pymavlink(master)$ MDEF=~/rc/ardupilot/modules/mavlink/message_definitions pip install . ``` Running `setup.py` is deprecated and is likely to break in the next...

@wasaybaig feel free to raise a PR against the MAVProxy wiki directly!

@Mac16661 it might be we want a float here instead, so we don't change the maths everywhere. @tridge ? Marking this for discussion tomorrow night.

Ping @Mac16661 - are you still interested in working on this issue?

OK, no answer from @Mac16661 here, closing this one., Please re-open if you want to pursue

Closing per directions in #28015

> We really should lock this in with a auto-test once we get them all documented again. Or maybe even have white list for logs that are "allowed" to be...

I've split the commits to conform to our standards. We have a document on cleaning commit up here: https://ardupilot.org/dev/docs/git-interactive-rebase.html This is to match our style requirements, linked from that page.