From 05d0265fef651de152c8127aa701e689555649f3 Mon Sep 17 00:00:00 2001 From: NAKAMURA Takumi Date: Mon, 18 Apr 2011 23:59:50 +0000 Subject: docs: Use as Heading elements instead of
. H1 ... doc_title H2 ... doc_section H3 ... doc_subsection H4 ... doc_subsubsection git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@129736 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/DeveloperPolicy.html | 39 ++++++++++++++++++--------------------- 1 file changed, 18 insertions(+), 21 deletions(-) (limited to 'docs/DeveloperPolicy.html') diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 633de1a..5d6c2d8 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -8,7 +8,7 @@ -
LLVM Developer Policy
+

LLVM Developer Policy

  1. Introduction
  2. Developer Policies @@ -34,7 +34,7 @@
    Written by the LLVM Oversight Team
    -
    Introduction
    +

    Introduction

    This document contains the LLVM Developer Policy which defines the project's @@ -63,7 +63,7 @@

    -
    Developer Policies
    +

    Developer Policies

    This section contains policies that pertain to frequent LLVM developers. We @@ -75,7 +75,7 @@

    -
    Stay Informed
    +

    Stay Informed

    Developers should stay informed by reading at least the "dev" mailing list for the projects you are interested in, such as @@ -102,7 +102,7 @@

    -
    Making a Patch
    +

    Making a Patch

    When making a patch for review, the goal is to make it as easy for the @@ -142,7 +142,7 @@

    -
    Code Reviews
    +

    Code Reviews

    LLVM has a code review policy. Code review is one way to increase the quality of software. We generally follow these policies:

    @@ -174,7 +174,7 @@
    -
    Code Owners
    +

    Code Owners

    The LLVM Project relies on two features of its process to maintain rapid @@ -225,7 +225,7 @@

    -
    Test Cases
    +

    Test Cases

    Developers are required to create test cases for any bugs fixed and any new features added. Some tips for getting your testcase approved:

    @@ -258,7 +258,7 @@
    -
    Quality
    +

    Quality

    The minimum quality standards that any change must satisfy before being committed to the main development branch are:

    @@ -318,8 +318,7 @@
    -
    - Obtaining Commit Access
    +

    Obtaining Commit Access

    We grant commit access to contributors with a track record of submitting high @@ -381,7 +380,7 @@

    -
    Making a Major Change
    +

    Making a Major Change

    When a developer begins a major new project with the aim of contributing it back to LLVM, s/he should inform the community with an email to @@ -410,8 +409,7 @@

    -
    Incremental Development -
    +

    Incremental Development

    In the LLVM project, we do all significant changes as a series of incremental patches. We have a strong dislike for huge changes or long-term development @@ -472,8 +470,7 @@

    -
    Attribution of -Changes
    +

    Attribution of Changes

    We believe in correct attribution of contributions to their contributors. However, we do not want the source code to be littered with random @@ -487,9 +484,9 @@ Changes

-
+

Copyright, License, and Patents -

+
@@ -507,7 +504,7 @@ Changes
-
Copyright
+

Copyright

The LLVM project does not require copyright assignments, which means that the @@ -530,7 +527,7 @@ Changes

-
License
+

License

We intend to keep LLVM perpetually open source and to use a liberal open source license. All of the code in LLVM is available under the @@ -585,7 +582,7 @@ Changes

-
Patents
+

Patents

To the best of our knowledge, LLVM does not infringe on any patents (we have actually removed code from LLVM in the past that was found to infringe). -- cgit v1.1