Restore release patches for Rolling. #1
Closed
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
cottsay
force-pushed
the
release/rolling/libg2o
branch
from
c00c9ad
to
a3d70a2
Compare
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.
When migrating Rolling to new platforms in ros/rosdistro#32036 a problem with the migration script (ros/rosdistro#32128) caused patches on release/, rpm/, and debian/ branches to be wiped out.
@croesmann with your approval I'll merge this PR and then bloom a debinc / release revision of ifm3d in order to restore this patch behavior. If this patch shouldn't be restored for some reason then this PR can just be closed.