Dan Albert

> The system should really be based on code owners. It is, but it doesn't auto-add reviewers. You would not believe the amount of spam we get. > Is this...

Oh, indeed it does. That's... misleading. And yes. When in doubt, bothering whatever droid you happen to know usually works.

https://source.android.com/docs/setup/contribute/submit-patches#request-review is more explicit, fwiw. That's the "full instructions" link at the top of the flow chart.

I find it's better to pick one at first. If a CL has ten reviewers assigned, everyone thinks someone else will do it, and so no one thinks it's their...

> He had suggested looking into ccache to improve build performance where static libraries shared between multiple Gradle modules are redundantly rebuilt. Fixing gradle so this isn't necessary sounds like...

FYI we're investigating shipping sccache in the SDK (https://github.com/android/ndk/issues/1790 shows how to use it yourself, but definitely read the readme in the sccache project that explains why what I've done...

Still there https://github.com/llvm/llvm-project/blob/894c22406f68af6574a62a40ec49e058344c324b/libcxx/include/__config#L1125-L1126 (that's a permalink, so it's _always_ going to say that). @rprichard, could you fix upstream at some point?

I know nothing about Dart.

It's probably going to be a while before I have the time to review this. I can't review and merge half of a PR. If the 7 things this PR...

afaik there's no expectation that the framework APIs are usable outside an app. If that's something you need, you need to file an OS bug against the framework: http://b.android.com.