Skip to content

docs: add note regarding MAVLink dialects#2729

Merged
julianoes merged 2 commits intomainfrom
pr-docs-mavlink-dialect
Dec 11, 2025
Merged

docs: add note regarding MAVLink dialects#2729
julianoes merged 2 commits intomainfrom
pr-docs-mavlink-dialect

Conversation

@julianoes
Copy link
Copy Markdown
Collaborator

@julianoes julianoes commented Dec 4, 2025

Closes #2691.

Review by commit. The second commit just fixes up some Windows file endings.

Here are some notes on how to change/set your own MAVLink dialect.
@julianoes julianoes force-pushed the pr-docs-mavlink-dialect branch from 7ca4ba8 to 159a618 Compare December 10, 2025 20:22
@julianoes julianoes force-pushed the pr-docs-mavlink-dialect branch from 159a618 to a9b608f Compare December 10, 2025 20:30
@sonarqubecloud
Copy link
Copy Markdown

Please retry analysis of this Pull-Request directly on SonarQube Cloud

@julianoes julianoes merged commit 9f4cbbd into main Dec 11, 2025
4 checks passed
@julianoes julianoes deleted the pr-docs-mavlink-dialect branch December 11, 2025 22:36
@julianoes
Copy link
Copy Markdown
Collaborator Author

Whoops, I messed that up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document/support process for using custom mavlink dialect

1 participant