Skip to content
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

Merged
merged 1 commit into from
Jun 30, 2016

Conversation

mikhail-matrosov
Copy link
Contributor

Bug fix: PLYReader would give corrupted colors if used in a parallel
code.

@SergioRAgostinho
Copy link
Member

Thanks. Could you please follow
http://pointclouds.org/documentation/advanced/pcl_style_guide.php#member-variables
http://pointclouds.org/documentation/advanced/pcl_style_guide.php#indentation-and-formatting

Also, add a comment explaining what those members are and initialize them properly in the class constructors.

@mikhail-matrosov
Copy link
Contributor Author

Renamed and initialized variables in comply with pcl guidelines, corrected indentation. Sorry for the previous commit =)

@SergioRAgostinho
Copy link
Member

Final comment. Could you please squash the commits into a single one.

@mikhail-matrosov
Copy link
Contributor Author

Done

@VictorLamoine
Copy link
Contributor

👍

@SergioRAgostinho
Copy link
Member

👍 thanks

@SergioRAgostinho
Copy link
Member

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.
@mikhail-matrosov
Copy link
Contributor Author

No problem

@SergioRAgostinho SergioRAgostinho merged commit e30228b into PointCloudLibrary:master Jun 30, 2016
animecomico pushed a commit to animecomico/pcl that referenced this pull request Aug 18, 2016
@SergioRAgostinho
Copy link
Member

This PR broke the pcl_io 1.8.0 ABI. We can always revert it temporarily before the release.

@taketwo
Copy link
Member

taketwo commented Jun 28, 2017

I'd say let's have a release candidate branch and revert it there?

@SergioRAgostinho
Copy link
Member

But then can we properly tag the main branch?

@jspricke
Copy link
Member

+1 for revert in release branch. (at tag is not associated with a branch ;) ).

@taketwo
Copy link
Member

taketwo commented Jun 28, 2017

Yes, we work with a release branch, eventually tag it's tip, and then wipe the branch.

@SergioRAgostinho SergioRAgostinho mentioned this pull request Jun 30, 2017
15 tasks
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.

5 participants