New REP 135 for Driver Namespaces #22
Merged
Conversation
This file contains 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
Proposed informational REP on driver namespaces.
|
It's mature enough to get a number. Please use 135. |
|
Posted to ROS Users on 2/20/2013. Will call a vote on 2/27/2013. |
|
@chadrockey: Please add a reference to the REP pointing to the discussion. |
|
@dirk-thomas I don't see where other REPs provide a reference to their own discussion. If this is expected, where should I place that reference? Is there a new header field? |
|
Just add it to a reference chapter at the end of the rep. |
|
@dirk-thomas References added. |
|
@tfoote This should be ready to merge. |
tfoote
added a commit
that referenced
this pull request
Mar 14, 2013
New REP 135 for Driver Namespaces Merging as Active
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.
Proposed informational REP on driver namespaces. Not sure if I should assign a number, so I did not do so to avoid conflicts.
As of 2/11/2013, this is under review in ros-sig-drivers@googlegroups.com