RST docs: convert HTML escapes to plain text in code examples.

[oota-llvm.git] / docs / DeveloperPolicy.rst

diff --git a/docs/DeveloperPolicy.rst b/docs/DeveloperPolicy.rst
index 96e4af332125bebb8519bda5019df902fe0f1407..f940dbc579a96dc83f6e602b1acfddd05c540f8b 100644 (file)
--- a/docs/DeveloperPolicy.rst
+++ b/docs/DeveloperPolicy.rst
@@ -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
 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?view=markup>`_
+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
@@ -302,7 +279,7 @@ If you have recently been granted commit access, these policies apply:
 #. You are granted *commit-after-approval* to all parts of LLVM.  To get
    approval, submit a `patch`_ to `llvm-commits
    <http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits>`_. When approved
-   you may commit it yourself.</li>
+   you may commit it yourself.
 
 #. You are allowed to commit patches without approval which you think are
    obvious. This is clearly a subjective decision --- we simply expect you to