From: Reid Spencer Date: Tue, 13 Feb 2007 09:20:14 +0000 (+0000) Subject: Clean up spelling mistakes. X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=80483bba3d35b86f73fbb6b233d3fe9ade70f517;p=oota-llvm.git Clean up spelling mistakes. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34238 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 78c0fb9a381..41bed52552c 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -66,7 +66,7 @@ commit form.
Commit
A change submitted directly to LLVM software - respository via the cvs commit command.
+ repository via the cvs commit command.
Developer
Anyone who submits a change to LLVM.
Increment
@@ -175,7 +175,7 @@ made by others.

Active developers must register an email account with bugzilla (http://llvm.org/bugs/) and preferably - subscribe to the llvm-bugs email list to keep track of bugs occuring in + subscribe to the llvm-bugs email list to keep track of bugs occurring in LLVM.

@@ -256,7 +256,7 @@
  • Code must compile cleanly on all platforms.
  • Code must pass the llvm-test test suite including SPEC CINT2000, SPEC CFP2000, SPEC CINT2006, and SPEC CFP2006.
  • -
  • The changesat must not cause performance or correctness regressions +
  • The change set must not cause performance or correctness regressions for the LLVM tools.
  • The changes must not cause performance or correctness regressions in code compiled with LLVM on all applicable targets.
  • @@ -271,7 +271,7 @@ apply:

    1. All feature and regression test cases must be added to the - llvm/test directory. The appropriate subdirectory should be + llvm/test directory. The appropriate sub-directory should be selected (see the Testing Guide for details.
    2. Test cases should be written in LLVM assembly language unless the @@ -393,7 +393,7 @@
    3. You are granted commit-after-approval to all parts of LLVM. To get approval, submit a patch to llvm-commits per the patch policies above. When approved you may commit it yourself.
    4. -
    5. You are granted commit-without-approavl to those portions of LLVM +
    6. You are granted commit-without-approval to those portions of LLVM that you own (contributed) or maintain (have been assigned responsibility for), with the proviso that such commits must not break the build. This is a "trust but verify" policy and commits of this nature are reviewed after @@ -402,7 +402,7 @@ be reverted. This is necessary when the change blocks other developers from making progress. The developers is welcome to re-commit the change after the problem has been fixed.
    7. -
    8. Multiple violations of these policies or a single aggregious violation +
    9. Multiple violations of these policies or a single egregious violation may cause commit access to be revoked, at the sole discretion of the LLVM Oversight Group.