denglesberg-splunk

Hey everybody, I ran into this issue too, and started thinking about how to fix it. It seems like the simplest way to handle a redirect given the existing abstractions...

Hi Yosi, What I'm saying is that based on the documentation, I expect that the custom `operator

If this is supposed to work (which is to say the `Message::operator

Would y'all be willing to accept a contribution to add support for this behavior?

I seem to have a similar/same problem in https://github.com/bazelbuild/rules_foreign_cc/issues/1034

[reproduction.tar.gz](https://github.com/bazelbuild/rules_foreign_cc/files/11122451/reproduction.tar.gz)

In the minimal reproduction, there are three files: `WORKSPACE.bazel` `BUILD.bazel` and `configure`. None of them appear to be modified by the `bazel` execution. The input file rule is: ``` filegroup(...

Thanks @alexeagle for the help - indeed the problem is with the glob exclude - it needs to exclude `bazel*/**` to actually exclude the bazel symlinks. I'll close this.