[llvm-commits] [llvm] r160776 - in /llvm/trunk: CODE_OWNERS.TXT docs/DeveloperPolicy.rst

[Sean Silva]

There seem to be a number of ways to do this with Sphinx. The best one
is probably:

http://sphinx.pocoo.org/markup/code.html#includes

--Sean Silva

On Thu, Jul 26, 2012 at 12:25 PM, Michael Spencer <bigcheesegs at gmail.com> wrote:
> On Thu, Jul 26, 2012 at 1:04 AM, Duncan Sands <baldrick at free.fr> wrote:
>> Author: baldrick
>> Date: Thu Jul 26 03:04:09 2012
>> New Revision: 160776
>>
>> URL: http://llvm.org/viewvc/llvm-project?rev=160776&view=rev
>> Log:
>> Add the list of code owners to the top level of the LLVM source tree to
>> 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.
>>
>> Added:
>>     llvm/trunk/CODE_OWNERS.TXT
>> Modified:
>>     llvm/trunk/docs/DeveloperPolicy.rst
>>
>> Added: llvm/trunk/CODE_OWNERS.TXT
>> URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/CODE_OWNERS.TXT?rev=160776&view=auto
>> ==============================================================================
>> --- llvm/trunk/CODE_OWNERS.TXT (added)
>> +++ llvm/trunk/CODE_OWNERS.TXT Thu Jul 26 03:04:09 2012
>> @@ -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 at 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 at math.spbu.ru
>> +D: Exception handling, debug information, and Windows codegen
>> +
>> +N: Ted Kremenek
>> +D: Clang Static Analyzer
>> +
>> +N: Chris Lattner
>> +E: sabre at nondot.org
>> +W: http://nondot.org/~sabre/
>> +D: Everything not covered by someone else
>> +
>> +N: John McCall
>> +E: rjmccall at apple.com
>> +D: Clang LLVM IR generation
>> +
>> +N: Jakob Olesen
>> +D: Register allocators and TableGen
>> +
>> +N: Duncan Sands
>> +E: baldrick at free.fr
>> +D: DragonEgg
>>
>> Modified: llvm/trunk/docs/DeveloperPolicy.rst
>> URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/DeveloperPolicy.rst?rev=160776&r1=160775&r2=160776&view=diff
>> ==============================================================================
>> --- llvm/trunk/docs/DeveloperPolicy.rst (original)
>> +++ llvm/trunk/docs/DeveloperPolicy.rst Thu Jul 26 03:04:09 2012
>> @@ -152,33 +152,10 @@
>>  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
>>  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
>> -current code owners are:
>> -
>> -* **Evan Cheng**: Code generator and all targets
>> -
>> -* **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
>> +code is appropriately reviewed, either by themself or by someone else.  The list
>> +of current code owners can be found in the file
>> +`CODE_OWNERS.TXT <http://llvm.org/viewvc/llvm-project/llvm/trunk/CODE_OWNERS.TXT>`_
>> +in the root of the LLVM source tree.
>>
>>  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
>>
>>
>> _______________________________________________
>> llvm-commits mailing list
>> llvm-commits at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
> Sphinx supports directly including the content of CODE_OWNERS.TXT in
> DeveloperPolicy.rst. Can we do this?
>
> - Michael Spencer
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits