maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

* Removed stray </p> tag 

* Whitespace cleanups

llvm-svn: 60891
This commit is contained in:
Misha Brukman 2008-12-11 19:44:51 +00:00
parent e4d722bf2f
commit 5039be7e27
1 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
llvm/docs/DeveloperPolicy.html
View File

@ -91,8 +91,8 @@
<div class="doc_text"> <div class="doc_text">
<p>When making a patch for review, the goal is to make it as easy for the <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> reviewer to read it as possible. As such, we recommend that you:</p>
<ol> <ol>
<li>Make your patch against the Subversion trunk, not a branch, and not an <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> 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> the time the patch was created and the time it is applied.</li>
<li>Patches should be made with this command: <li>Patches should be made with this command:
<pre>svn diff -x -u</pre> <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 or with the utility <tt>utils/mkpatch</tt>, which makes it easy to read the
diff.</li> diff.</li>
<li>Patches should not include differences in generated code such as the <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 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> <tt>utils/mkpatch</tt> utility takes care of this for you.</li>
</ol> </ol>
<p>When sending a patch to a mailing list, it is a good idea to send it as an <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: <tt>Content-Disposition: inline</tt> rather than <tt>Content-Disposition:
attachment</tt>. Apple Mail gamely displays such a file inline, making it attachment</tt>. Apple Mail gamely displays such a file inline, making it
difficult to work with for reviewers using that program.</p> difficult to work with for reviewers using that program.</p>
</p>
</div> </div>
<!-- _______________________________________________________________________ --> <!-- _______________________________________________________________________ -->