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

Fix some errors in some probably not frequented code paths melodic #1415

Conversation

awesomebytes
Copy link
Contributor

Update to #1410

Are you gonna backport to Kinetic also?

@dirk-thomas
Copy link
Member

#1410 had some additional changes. Are they not applicable to the Melodic branch? Should they be pull requested against an older branch only? If yes, which one would be newest distro which needs those?

Are you gonna backport to Kinetic also?

All patches are considered for backporting. Since this fixes obvious bugs it will very likely be backported for the next patch release.

@awesomebytes
Copy link
Contributor Author

awesomebytes commented May 31, 2018 via email

@dirk-thomas
Copy link
Member

So if the file gets backported as it is (which looks more correct) it
should be all fine.

The "file" doesn't get backported only the applied patches get cherry-picked to the older branches.

So if older distros need additional fixes please create a separate PR for that targeting the branch with the most recent distro which needs the fix.

@awesomebytes
Copy link
Contributor Author

awesomebytes commented May 31, 2018 via email

@awesomebytes awesomebytes changed the title Fix some errors in some probably not frequented code paths Fix some errors in some probably not frequented code paths melodic Jun 6, 2018
@awesomebytes
Copy link
Contributor Author

I opened PR on all in-development distros.

Indigo and Kinetic have the same changes.

Lunar and Melodic have the same changes.

I don't know what's the process to apply the same change to all the branches, sorry if this is not in your expected format.

@dirk-thomas
Copy link
Member

Thanks for the patch!

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

Successfully merging this pull request may close these issues.

3 participants