diff options
Diffstat (limited to 'docs/DeveloperPolicy.html')
-rw-r--r-- | docs/DeveloperPolicy.html | 17 |
1 files changed, 6 insertions, 11 deletions
diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 357c92956f..829860ccaa 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -107,18 +107,13 @@ patches may not apply correctly if the underlying code changes between the time the patch was created and the time it is applied.</li> - <li>Patches should be made with this command: -<div class="doc_code"> -<pre> -svn diff -</pre> -</div> - or with the utility <tt>utils/mkpatch</tt>, which makes it easy to read - the diff.</li> + <li>Patches should be made with <tt>svn diff</tt>, or similar. If you use + a different tool, make sure it uses the <tt>diff -u</tt> format and + that it doesn't contain clutter which makes it hard to read.</li> - <li>Patches should not include differences in generated code such as the code - generated by <tt>autoconf</tt> or <tt>tblgen</tt>. The - <tt>utils/mkpatch</tt> utility takes care of this for you.</li> + <li>If you are modifying generated files, such as the top-level + <tt>configure</tt> script, please separate out those changes into + a separate patch from the rest of your changes.</li> </ol> <p>When sending a patch to a mailing list, it is a good idea to send it as an |