stdcxx-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r425219 - /incubator/stdcxx/site/bugs.html
Date Mon, 24 Jul 2006 23:14:27 GMT
Author: sebor
Date: Mon Jul 24 16:14:27 2006
New Revision: 425219

2006-07-24  Martin Sebor  <>

	* bugs.html: Added a section describing how to submit new files
	as part of a patch.


Modified: incubator/stdcxx/site/bugs.html
--- incubator/stdcxx/site/bugs.html (original)
+++ incubator/stdcxx/site/bugs.html Mon Jul 24 16:14:27 2006
@@ -138,6 +138,7 @@
         <li><a href="#report">Reporting a Bug</a></li>
         <li><a href="#patches">Submitting Patches</a></li>
         <li><a href="#patch_format">Patch Format</a></li>
+        <li><a href="#new_files">New Files</a></li>
@@ -387,19 +388,42 @@
 diff</code></a>  command  by  default  as   well  as  by  the  GNU  <a
-utility     and    understood     by    GNU     <a    class="external"
-creating patches  on Windows it's important  to keep in  mind that the
-newline sequences (carriage-return followed by line-feed, or <CR><LF>)
-may not be recognized by traditional UNIX implementations of the patch
-utility (as  is the case on  Solaris). For portability, it  is best to
-strip  the carriage-returns  from  the patch  before  posting it.  The
-standard                      <a                      class="external"
+utility      and      understood      by      <a      class="external"
+patch</code></a>. When  creating patches on Windows it is important to
+keep in  mind that the newline sequences  (carriage-return followed by
+line-feed,  or <CR><LF>)  may not  be recognized  by  traditional UNIX
+implementations of the patch utility  (as is the case on Solaris). For
+portability, it is  best to strip the carriage-returns  from the patch
+before    posting    it.     The    standard    <a    class="external"
 utility can be used to do that.
+    <a name="new_files"></a>
+    <h2 class="boxed">New Files</h2>
+    <div class="section">
+      <p>
+New files  included as part of a  patch (such as new  tests) should be
+submitted  in  the  original format  and  not  as  the output  of  the
+<code>patch</code> utility since  <code>patch</code> cannot create
+files.  Multiple files  can be submitted individually or  as a gzipped
+tarball. Be  aware of the size  limit imposed on posts  to the mailing
+list. In general,  it is better to avoid posting  very large files and
+instead attach them to an issue in the bug tracking database.
+      </p>
+      <p>
+Each  new source  or header  file  should contain  the license  header
+described                  in                  the                  <a
+href="">ASF  Source Header
+and Copyright Notice Policy</a>.
+      </p>
     <!-- End main content -->
@@ -411,7 +435,7 @@
           |start bottomstrip
       <div class="copyright">
-           Copyright &copy; 2005 The Apache Software Foundation.
+           Copyright &copy; 2006 The Apache Software Foundation.

View raw message