-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(launch): adding v4l2 buffer timestamp and image_transport options to launch file #22
Conversation
Signed-off-by: Yuxuan Liu <[email protected]>
By the way, I think it is not really good that I can directly merge the PR myself. I will wait for a review first.. |
Signed-off-by: Yuxuan Liu <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the PR! Just a minor wording change suggestion, otherwise looks good.
Signed-off-by: Yuxuan Liu <[email protected]>
Thank you for the review. I updated the documents. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: just noticed an extra space.
Signed-off-by: Yuxuan Liu <[email protected]>
feat(launch): adding v4l2 buffer timestamp and image_transport options to launch file
feat(launch): adding v4l2 buffer timestamp and image_transport options to launch file Co-authored-by: David Wong <[email protected]>
Description
We have PR #9 introducing
use_v4l2_buffer_timestamps
flag into the node and PR #14 introducinguse_image_transport
flag into the node. But They do not appear in the launch file, which could confuse users.