A step towards geting linux ppc to work (see PR 3099)

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

diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index 18c1ff34ac273e6aa53550bc1aff69be0a932b44..689bcb0783b21150c5c6ce06cd1d26e54c18101d 100644 (file)
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -116,6 +116,15 @@
   <em>attachment</em> to the message, not embedded into the text of the
   message.  This ensures that your mailer will not mangle the patch when it 
   sends it (e.g. by making whitespace changes or by wrapping lines).</p>
+  
+  <p><em>For Thunderbird users:</em> Before submitting a patch, please open 
+  <em>Preferences &#8594; Advanced &#8594; General &#8594; Config Editor</em>,
+  find the key <tt>mail.content_disposition_type</tt>, and set its value to
+  <tt>1</tt>. Without this setting, Thunderbird sends your attachment using
+  <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>
 
 <!-- _______________________________________________________________________ -->
@@ -236,7 +245,8 @@
     <li>The code must not cause regressions on a reasonable subset of llvm-test,
         where "reasonable" depends on the contributor's judgement and the scope
         of the change (more invasive changes require more testing). A reasonable
-        subset is "<tt>llvm-test/MultiSource/Benchmarks</tt>".</li>
+        subset might be something like
+        "<tt>llvm-test/MultiSource/Benchmarks</tt>".</li>
   </ol>
   <p>Additionally, the committer is responsible for addressing any problems
   found in the future that the change is responsible for.  For example:</p>
@@ -418,11 +428,12 @@ Changes</a></div>
   <p>We believe in correct attribution of contributions to 
   their contributors.  However, we do not want the source code to be littered
   with random attributions "this code written by J Random Guy" (this is noisy
-  and distracting.  In practice, the revision control system keeps a perfect
-  history of who change what, and the CREDITS.txt file describes higher-level
-  contributions.</p>
+  and distracting).  In practice, the revision control system keeps a perfect
+  history of who changed what, and the CREDITS.txt file describes higher-level
+  contributions.  If you commit a patch for someone else, please say "patch 
+  contributed by J Random Guy!" in the commit message.</p>
 
-  <p>Overall, please do not add contributor names to the source base.</p>
+  <p>Overall, please do not add contributor names to the source code.</p>
 </div>
 
 
@@ -458,7 +469,7 @@ Changes</a></div>
   
   <p>
   Although UIUC may eventually reassign the copyright of the software to another
-  entity (e.g. a dedicated non-profit "LLVM Organization", or something)
+  entity (e.g. a dedicated non-profit "LLVM Organization")
   the intent for the project is to always have a single entity hold the
   copyrights to LLVM at any given time.</p>
   
@@ -467,6 +478,7 @@ Changes</a></div>
   reduces the managerial burden for any kind of administrative or technical 
   decisions about LLVM.  The goal of the LLVM project is to always keep the code
   open and <a href="#license">licensed under a very liberal license</a>.</p>
+
 </div>
 
 <!-- _______________________________________________________________________ -->
@@ -480,7 +492,8 @@ Changes</a></div>
   <ul>
     <li>You can freely distribute LLVM.</li>
     <li>You must retain the copyright notice if you redistribute LLVM.</li>
-    <li>Binaries derived from LLVM must reproduce the copyright notice.</li>
+    <li>Binaries derived from LLVM must reproduce the copyright notice (e.g. 
+        in an included readme file).</li>
     <li>You can't use our names to promote your LLVM derived products.</li>
     <li>There's no warranty on LLVM at all.</li>
   </ul>
@@ -520,9 +533,11 @@ Changes</a></div>
    arbitrary purposes (including commercial use).</p>
    
 <p>When contributing code, we expect contributors to notify us of any potential
-   for patent-related trouble with their changes.  If you own the rights to a
+   for patent-related trouble with their changes.  If you or your employer
+   own the rights to a
    patent and would like to contribute code to LLVM that relies on it, we
-   require that you sign an agreement that allows any other user of LLVM to
+   require that
+   the copyright owner sign an agreement that allows any other user of LLVM to
    freely use your patent.  Please contact the <a 
    href="mailto:llvm-oversight@cs.uiuc.edu">oversight group</a> for more
    details.</p>
@@ -537,6 +552,11 @@ Changes</a></div>
   the entire software base can be managed by a single copyright holder.  This
   implies that any contributions can be licensed under the license that the
   project uses.</p>
+
+  <p>When contributing code, you also affirm that you are legally entitled to 
+  grant this copyright, personally or on behalf of your employer.  If the code
+  belongs to some other entity, please raise this issue with the oversight
+  group before the code is committed.</p>
 </div>
 
 <!-- *********************************************************************** -->