search for: wciia

> Understanding the internal llvm/clang structure is easy, > deducing the correct code owner is not due to the > vague and changing nature of the CODE_OWNERS.TXT Does not seem to me and many people around. If in doubt - ask at ML or IRC. > "Exception handling, Windows codegen, ARM EABI" Just for your information - this covers some lines in some files in llvm/CodeGen, some

>> This approach is fine for casual reader but >> does not work for scripting or any automated >> way of dealing with the build. > Will you please clarify how the automation / scripting helps with the > patch approval process? Generally release patch process works like this: - patch gets checked-in on the trunk - developer sends message to the code owner who approves

...efixes]) if args.verbose: - print >>sys.stderr, 'Rewriting FileCheck prefixes: %s' % (prefix_set,) + print('Rewriting FileCheck prefixes: %s' % (prefix_set,), file=sys.stderr) fixed_lines = [] for l in test_lines: if is_in_function_start: Index: wciia.py =================================================================== --- wciia.py (revision 249819) +++ wciia.py (working copy) @@ -20,6 +20,7 @@ """ +from __future__ import print_function import os code_owners = {} @@ -42,7 +43,7 @@ if 'filesfolders' in owner:...