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

Remove unused config_setting targets from //third_party. #24898

Closed
wants to merge 1 commit into from

Conversation

katre
Copy link
Member

@katre katre commented Jan 10, 2025

These refer to the deprecated --host_cpu flag, which is bad to select on anyway.

These refer to the deprecated `--host_cpu` flag, which is bad to select
on anyway.
@katre katre changed the title [WIP] Remove unused config_setting targets from //third_party. Remove unused config_setting targets from //third_party. Jan 10, 2025
@katre katre requested a review from gregestren January 10, 2025 16:44
@katre katre marked this pull request as ready for review January 10, 2025 16:44
@github-actions github-actions bot added the awaiting-review PR is awaiting review from an assigned reviewer label Jan 10, 2025
@github-actions github-actions bot removed the awaiting-review PR is awaiting review from an assigned reviewer label Jan 10, 2025
@katre katre deleted the remove_tp_host_cpu branch January 14, 2025 16:10
fmeum pushed a commit to fmeum/bazel that referenced this pull request Jan 14, 2025
These refer to the deprecated `--host_cpu` flag, which is bad to select on anyway.

Closes bazelbuild#24898.

PiperOrigin-RevId: 714169621
Change-Id: I97c751cd781f0ccbd0a36086fe4f6c927b1a3d8d
fmeum pushed a commit to fmeum/bazel that referenced this pull request Jan 29, 2025
These refer to the deprecated `--host_cpu` flag, which is bad to select on anyway.

Closes bazelbuild#24898.

PiperOrigin-RevId: 714169621
Change-Id: I97c751cd781f0ccbd0a36086fe4f6c927b1a3d8d
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.

2 participants