You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stdcxx.apache.org by se...@apache.org on 2006/07/25 01:14:27 UTC
svn commit: r425219 - /incubator/stdcxx/site/bugs.html
Author: sebor
Date: Mon Jul 24 16:14:27 2006
New Revision: 425219
URL: http://svn.apache.org/viewvc?rev=425219&view=rev
Log:
2006-07-24 Martin Sebor <se...@roguewave.com>
* bugs.html: Added a section describing how to submit new files
as part of a patch.
Modified:
incubator/stdcxx/site/bugs.html
Modified: incubator/stdcxx/site/bugs.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/site/bugs.html?rev=425219&r1=425218&r2=425219&view=diff
==============================================================================
--- 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>
</ul>
</div>
@@ -387,19 +388,42 @@
diff</code></a> command by default as well as by the GNU <a
class="external"
href="http://www.gnu.org/software/diffutils/diffutils.html"><code>diff</code></a>
-utility and understood by GNU <a class="external"
-href="http://www.gnu.org/software/patch/patch.html"><code>patch</code></a>. When
-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"
+href="http://www.gnu.org/software/patch/patch.html"><code>GNU
+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"
href="http://www.opengroup.org/onlinepubs/009695399/utilities/tr.html">tr</a>
utility can be used to do that.
</li>
</ol>
+
+ <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 new
+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="http://www.apache.org/legal/src-headers.html">ASF Source Header
+and Copyright Notice Policy</a>.
+
+ </p>
</div>
<!-- End main content -->
@@ -411,7 +435,7 @@
|start bottomstrip
+-->
<div class="copyright">
- Copyright © 2005 The Apache Software Foundation.
+ Copyright © 2006 The Apache Software Foundation.
</div>
</div>
</body>