-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
PLYReader: thread safe colors #1587
PLYReader: thread safe colors #1587
Conversation
Thanks. Could you please follow Also, add a comment explaining what those members are and initialize them properly in the class constructors. |
Renamed and initialized variables in comply with pcl guidelines, corrected indentation. Sorry for the previous commit =) |
Final comment. Could you please squash the commits into a single one. |
2cf5f71
to
0838a52
Compare
Done |
👍 |
👍 thanks |
Sorry to be picky once again, can you amend the commit message. You concatenated the message from the three commits you squashed. |
Bug fix: PLYReader would give corrupted colors if used in a parallel code.
0838a52
to
4c57676
Compare
No problem |
PLYReader: thread safe colors
This PR broke the pcl_io 1.8.0 ABI. We can always revert it temporarily before the release. |
I'd say let's have a release candidate branch and revert it there? |
But then can we properly tag the main branch? |
+1 for revert in release branch. (at tag is not associated with a branch ;) ). |
Yes, we work with a release branch, eventually tag it's tip, and then wipe the branch. |
Bug fix: PLYReader would give corrupted colors if used in a parallel
code.