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

Merge r330788 into the 6.0 branch : Bring r329960 back. #36838

Closed
tstellar opened this issue May 16, 2018 · 5 comments
Closed

Merge r330788 into the 6.0 branch : Bring r329960 back. #36838

tstellar opened this issue May 16, 2018 · 5 comments
Assignees
Labels
bugzilla Issues migrated from bugzilla wontfix Issue is real, but we can't or won't fix it. Not invalid

Comments

@tstellar
Copy link
Collaborator

Bugzilla Link 37490
Resolution WONTFIX
Resolved on May 30, 2018 12:05
Version 6.0
OS All
Blocks #35997
Fixed by commit(s) r330788

Extended Description

Is it OK to merge the following revision(s) to the 6.0 branch?

@tstellar
Copy link
Collaborator Author

assigned to @andrewrk

@tstellar
Copy link
Collaborator Author

@tstellar
Copy link
Collaborator Author

r329960 was committed to master after the release_60 branch was made, do we really need this fix?

@andrewrk
Copy link
Member

I'm fine with waiting until llvm 7 for this fix if it seems risky to backport.

@tstellar
Copy link
Collaborator Author

Ok, let's wait then.

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
@Quuxplusone Quuxplusone added the wontfix Issue is real, but we can't or won't fix it. Not invalid label Jan 20, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla wontfix Issue is real, but we can't or won't fix it. Not invalid
Projects
None yet
Development

No branches or pull requests

3 participants