search for: 2bfdad11

..., trivial patches, like documenting a function which is missing documentation (your patches show that you apparently know the code quite well, an advantage I didn't have), or even just spelling fixes (don't go overboard though). That helps grease the wheels. Look at c27faccb in llvm.git and 2bfdad11 in clang.git for my first two patches, which I caught simply because I was self-hosting with a bleeding-edge clang with the latest warnings turned on. > As a code owner I would think it would be nice to see a consolidated list of > the open patches for your area. I suppose it would also be n...

I think the main benefit of a scheme like this would be that a pull request tells a code owner which patches require their attention. As a contributor it would be nice to see your patch in a queue somewhere rather than just be buried down the mailing list. When patches are sent to llvm-commits it can be hard to tell if a code owner has noticed the patch because it is a very high-volume list.