remove rosgraph_msgs and std_srvs (moved to separate repo) #355
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
|
+1 |
1 similar comment
|
+1 |
dirk-thomas
added a commit
that referenced
this pull request
Feb 11, 2014
remove rosgraph_msgs and std_srvs (moved to separate repo)
contradict
pushed a commit
to contradict/ros_comm
that referenced
this pull request
Aug 12, 2016
Remove repeated prefices from buttons
rsinnet
pushed a commit
to MisoRobotics/ros_comm
that referenced
this pull request
Jun 19, 2017
remove rosgraph_msgs and std_srvs (moved to separate repo)
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.
The message packages
rosgraph_msgsandstd_srvsmust be moved to a separate repo (https://github.com/ros/ros_comm_msgs) since currently there is a circular dependency which prevents releasing both repos into Indigo.ros_commdepends onroslispwhich depends on those two packages insideros_comm.While this also applies to Groovy and Hydro I am not planning to split it for them since the repos are already released and therefore the circular dependency does not pose a problem anymore.
@tfoote @wjwwood Please review.