Skip to content

Conversation

@airballking
Copy link
Contributor

Should be merged after cram-code/cram_3rdparty#3 has been confirmed and merged.

@gaya-
Copy link
Member

gaya- commented Dec 4, 2014

This is not 3rd party code, Lorenz wrote this. But I agree that it should better be somewhere else. What about a cram_utililities repo / metapackage where all these kind of things could go?

@gaya-
Copy link
Member

gaya- commented Jul 20, 2015

I propose to move this to roslisp_common. In order to get rid of dependency on split-sequence cl-utils:tokenize from package roslisp_utilities can be used instead. Should I go ahead and make a pull request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants