os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add a new paragraph to the suggestions section stating that

Browse source 
style/whitespace changes should not be mixed with functionality/content
changes but should be done in separate commits.

Requested by:	obrien
This commit is contained in:
John Baldwin 2000-01-22 04:15:21 +00:00
parent b9951cd883
commit 20193a67fe
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=6414
2 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
en_US.ISO8859-1/articles/committers-guide/article.sgml
View file

@ -781,6 +781,14 @@
man page to verify the all of the cross references and file references
are correct and that the man page has all of the appropriate
<makevar>MLINK</makevar>s installed.</para>
<para>Do not mix style fixes with new functionality. It makes
the diffs hard to read, and hides the new bugs. Do not
include whitespace changes with content changes in commits to
<filename>doc/</filename> or <filename>www/</filename>. It
makes the translators' job much more difficult. Instead, make any
style or whitespace changes in seperate commits that are clearly
labeled as such in the commit message.</para>
</sect2>
</sect1>

8
en_US.ISO_8859-1/articles/committers-guide/article.sgml
View file

@ -781,6 +781,14 @@
man page to verify the all of the cross references and file references
are correct and that the man page has all of the appropriate
<makevar>MLINK</makevar>s installed.</para>
<para>Do not mix style fixes with new functionality. It makes
the diffs hard to read, and hides the new bugs. Do not
include whitespace changes with content changes in commits to
<filename>doc/</filename> or <filename>www/</filename>. It
makes the translators' job much more difficult. Instead, make any
style or whitespace changes in seperate commits that are clearly
labeled as such in the commit message.</para>
</sect2>
</sect1>