-
Notifications
You must be signed in to change notification settings - Fork 4
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
48 adding fmcw nodes to existing develop branch being required #49
base: develop
Are you sure you want to change the base?
48 adding fmcw nodes to existing develop branch being required #49
Conversation
Signed-off-by: TimoHinsemann <timo.hinsemann@persival.de>
…apping nodes not regarded yet, redundancy of nodes possible for now). Also tags are added for each FMCW-Node. Signed-off-by: TimoHinsemann <timo.hinsemann@persival.de>
src
Outdated
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.
This does not point to a commit on the main branch. The source repo need to be updated first, so lidar-limbs is not pointing to a feature branch which might not exist anymore in the future.
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.
Okay makes sense, so we should maybe talk soon about the repo-changes and if they are acceptable for the main-branch
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.
Please create a pull request in https://github.com/PerCollECT/Source-Files
Fixes #36 , #42 , #45 and #48.
Changes are already discussed with @ChristophPopp - Merging to develop-branch seems right for now. (?)