6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-08-09 11:25:55 +00:00
Code Issues Projects Releases Wiki Activity

Add the list of code owners to the top level of the LLVM source tree to

Browse Source 
hopefully make it more visible.  Adjust the web-docs to have a link to
this file rather than the list itself.  I described code owners as also
being gatekeepers for their part of the code, which I think is true but
isn't in the code owner explanation on the web page.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@160776 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Duncan Sands
2012-07-26 08:04:09 +00:00
parent 7f76cb6666
commit 35b87607b6
2 changed files with 55 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
CODE_OWNERS.TXT Normal file
View File

@@ -0,0 +1,51 @@
This file is a list of the people responsible for ensuring that patches for a
particular part of LLVM are reviewed, either by themself or by someone else.
They are also the gatekeepers for their part of LLVM, with the final word on
what goes in or not.
The list is sorted by surname and formatted to allow easy grepping and
beautification by scripts. The fields are: name (N), email (E), web-address
(W), PGP key ID and fingerprint (P), description (D), and snail-mail address
(S).
N: Evan Cheng
E: evan.cheng@apple.com
D: Code generator and all targets
N: Greg Clayton
D: LLDB
N: Peter Collingbourne
D: libclc
N: Doug Gregor
D: Clang Frontend Libraries
N: Tobias Grosser
D: Polly
N: Howard Hinnant
D: libc++
N: Anton Korobeynikov
E: asl@math.spbu.ru
D: Exception handling, debug information, and Windows codegen
N: Ted Kremenek
D: Clang Static Analyzer
N: Chris Lattner
E: sabre@nondot.org
W: http://nondot.org/~sabre/
D: Everything not covered by someone else
N: John McCall
E: rjmccall@apple.com
D: Clang LLVM IR generation
N: Jakob Olesen
D: Register allocators and TableGen
N: Duncan Sands
E: baldrick@free.fr
D: DragonEgg

31
docs/DeveloperPolicy.rst
View File

@@ -152,33 +152,10 @@ committed are reviewed after they go in: you don't want everyone to assume
someone else will review it, allowing the patch to go unreviewed. To solve this someone else will review it, allowing the patch to go unreviewed. To solve this
problem, we have a notion of an 'owner' for a piece of the code. The sole problem, we have a notion of an 'owner' for a piece of the code. The sole
responsibility of a code owner is to ensure that a commit to their area of the responsibility of a code owner is to ensure that a commit to their area of the
code is appropriately reviewed, either by themself or by someone else. The code is appropriately reviewed, either by themself or by someone else. The list
current code owners are: of current code owners can be found in the file
`CODE_OWNERS.TXT <http://llvm.org/viewvc/llvm-project/llvm/trunk/CODE_OWNERS.TXT>`_
* **Evan Cheng**: Code generator and all targets in the root of the LLVM source tree.
* **Greg Clayton**: LLDB
* **Doug Gregor**: Clang Frontend Libraries
* **Howard Hinnant**: libc++
* **Anton Korobeynikov**: Exception handling, debug information, and Windows
codegen
* **Ted Kremenek**: Clang Static Analyzer
* **Chris Lattner**: Everything not covered by someone else
* **John McCall**: Clang LLVM IR generation
* **Jakob Olesen**: Register allocators and TableGen
* **Duncan Sands**: dragonegg and llvm-gcc 4.2
* **Peter Collingbourne**: libclc
* **Tobias Grosser**: polly
Note that code ownership is completely different than reviewers: anyone can Note that code ownership is completely different than reviewers: anyone can
review a piece of code, and we welcome code review from anyone who is review a piece of code, and we welcome code review from anyone who is