Author: breser
Date: Wed Dec 12 03:31:19 2012
New Revision: 1420516
URL: http://svn.apache.org/viewvc?rev=1420516&view=rev
Log:
Try to direct people to our coding conventions not just for log messages
in the patch submission section of the community guide.
* publish/docs/community-guide/general.part.html
(patches): Add pointer to Coding Conventions under feedback paragraph.
Modified:
subversion/site/publish/docs/community-guide/general.part.html
Modified: subversion/site/publish/docs/community-guide/general.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/general.part.html?rev=1420516&r1=1420515&r2=1420516&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/general.part.html (original)
+++ subversion/site/publish/docs/community-guide/general.part.html Wed Dec 12
03:31:19 2012
@@ -635,7 +635,10 @@ code submission, and it's a rare patch t
little room for improvement. After discussing people's responses to
your patch, make the appropriate changes and resubmit, wait for the
next round of feedback, and lather, rinse, repeat, until some
-committer applies it.</p>
+committer applies it. You can avoid some iterations by reviewing
+and applying the project's
+<a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->">Coding Conventions</a>
+to your patch before submitting it.</p>
<p>If you don't get a response for a while, and don't see the patch
applied, it may just mean that people are really busy. Go ahead and
