-
Notifications
You must be signed in to change notification settings - Fork 592
[email protected] #6435
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
base: main
Are you sure you want to change the base?
[email protected] #6435
Conversation
|
Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (numactl) have been updated in this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces the numactl module, version 2.0.19, to the Bazel Central Registry. The submission is well-structured, adheres to most BCR policies, and includes a comprehensive test module. I have a couple of suggestions for the BUILD.bazel overlay to improve correctness and usability. Additionally, as per the BCR style guide's strong suggestions, it would be beneficial to add a README.md in the modules/numactl/2.0.19/overlay/ directory to document the creation process of the BUILD.bazel file.
d2fefb4 to
c5c9fc7
Compare
|
@meteorcloudy friendly ping! |
|
@fmeum if you have a sec could I get a review on this one? |
| ) | ||
|
|
||
| # Common compiler flags | ||
| COMMON_COPTS = ["-Wall"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't this cause warning spam if consumers use a different compiler? Protobuf has been doing this forever and it's always been very painful.
No description provided.