-
Notifications
You must be signed in to change notification settings - Fork 249
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(build): special case inconsistently-cased paths in LLVM build #4540
Conversation
Co-authored-by: John Edmonds <john.a.edmonds@gmail.com>
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Co-authored-by: John Edmonds <john.a.edmonds@gmail.com>
Ugh, I knew I shouldn't have done that. @johnedmonds any chance you can go to https://cla.developers.google.com/ and sign the Google CLA? Our compliance bot is picky and because I applied the changes from the web UI rather than manually it's going to attribute them to you. If you don't want to sign the CLA I can (probably?) revert the auto-commits and make the fixes myself. |
Sorry about that. Any chance you could change the author to jedmonds@spotify.com which has signed the CLA? (I just changed the default address on my profile page if that helps.) Otherwise, you can just revert and re-apply the changes yourself. |
I don't believe I can (or at least, have no idea how I would), but I believe you should be able to add the @gmail.com address at the linked page? |
Done. Signed the CLA 👍 . |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
Fixes #4535