Tony Aiuto
Tony Aiuto
cc: @gregestren
I think we should merge it. I no longer have merge rights, so I didn't do it myself.
No worries. I am weeks behind on all my Bazel projects.
I get this. It is debian rodete, so rolling release near head. ``` PRETTY_NAME="Debian GNU/Linux rodete" NAME="Debian GNU/Linux rodete" VERSION_CODENAME=rodete ID=debian ```
Whoops. That should have been part of #287. Yes. This is indeed missing. It should follow the pattern of --stamp that the other rules do.
[discussion] Decide whether or not to express FPU nuances for `@platforms//cpu:armv*-m*` constraints
Agreed. The various features which pop up in each architecture should be listed as individual constraints. We got to the state we are in by trying to quickly acomodate existing...
The fix we would like to make is to split rules_license into two modules in the same repo. One with just the declarations and one with the tools. It will...
The approach I may prototype is to: - have rules_go add bazel-contrib/supply-chain metadata to the generated BUILD files - modify go_binary to gather those markers and use that This can...
Sorry I lost track of this. Can you git pull and push again to bring the branches in line. I seem unable to merge it right now.
Sigh..... I don't know what is going on with github here. It just keeps saying your branch is out of date with main. I'll try a command line merge.