MAVFTP URL clarifications#721
Merged
Merged
Conversation
julianoes
approved these changes
Jun 17, 2026
Collaborator
Author
|
@peterbarker Any comments. I plan to merge this next time I'm around. |
Collaborator
Author
|
OK, everyone has had a chance to look at this. Thanks @julianoes |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This updates the mavftp URL section to match the proposal from the 20260603 -Dev-Meeting, as outline by @julianoes in mavlink/mavlink#2484 (comment)
@peterbarker This is the following, where you can't have an absolute path with
@SOMEDIR:Fixes mavlink/mavlink#2484