diff options
| author | Misha Brukman <brukman+llvm@gmail.com> | 2008-12-11 19:44:51 +0000 |
|---|---|---|
| committer | Misha Brukman <brukman+llvm@gmail.com> | 2008-12-11 19:44:51 +0000 |
| commit | 66286e9e61d18c04451865922097852a3792e5be (patch) | |
| tree | acc1ff009e20e1cb5c1568bcd936c31a05d3be78 /docs/DeveloperPolicy.html | |
| parent | 2d33c5443a5af06852ca172e60d48837ab9f352c (diff) | |
* Removed stray </p> tag
* Whitespace cleanups
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@60891 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/DeveloperPolicy.html')
| -rw-r--r-- | docs/DeveloperPolicy.html | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 6ea772407e..c2b1ca1326 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -91,8 +91,8 @@ <div class="doc_text"> -<p>When making a patch for review, the goal is to make it as easy for the - reviewer to read it as possible. As such, we recommend that you:</p> + <p>When making a patch for review, the goal is to make it as easy for the + reviewer to read it as possible. As such, we recommend that you:</p> <ol> <li>Make your patch against the Subversion trunk, not a branch, and not an old version of LLVM. This makes it easy to apply the patch.</li> @@ -102,14 +102,13 @@ the time the patch was created and the time it is applied.</li> <li>Patches should be made with this command: - <pre>svn diff -x -u</pre> - or with the utility <tt>utils/mkpatch</tt>, which makes it easy to read the - diff.</li> + <div class="doc_code"><pre>svn diff -x -u</pre></div> + or with the utility <tt>utils/mkpatch</tt>, which makes it easy to read the + diff.</li> <li>Patches should not include differences in generated code such as the code generated by <tt>flex</tt>, <tt>bison</tt> or <tt>tblgen</tt>. The <tt>utils/mkpatch</tt> utility takes care of this for you.</li> - </ol> <p>When sending a patch to a mailing list, it is a good idea to send it as an @@ -124,7 +123,6 @@ <tt>Content-Disposition: inline</tt> rather than <tt>Content-Disposition: attachment</tt>. Apple Mail gamely displays such a file inline, making it difficult to work with for reviewers using that program.</p> -</p> </div> <!-- _______________________________________________________________________ --> |