@@ -387,19 +388,42 @@
diff command by default as well as by the GNU diff
-utility and understood by GNU patch. When
-creating patches on Windows it's important to keep in mind that the
-newline sequences (carriage-return followed by line-feed, or )
-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 GNU
+patch. When creating patches on Windows it is important to
+keep in mind that the newline sequences (carriage-return followed by
+line-feed, or ) 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 tr
utility can be used to do that.
+
+
+

New Files

+

+

+
+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
+patch utility since patch 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.
+
+