You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by da...@apache.org on 2010/11/30 10:57:15 UTC
svn commit: r1040451 -
/subversion/site/publish/docs/community-guide/general.part.html
Author: danielsh
Date: Tue Nov 30 09:57:15 2010
New Revision: 1040451
URL: http://svn.apache.org/viewvc?rev=1040451&view=rev
Log:
* /site/publish/docs/community-guide/general.part.html
(#patches): Clarify that feedbacks are not to be taken as instructions.
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=1040451&r1=1040450&r2=1040451&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/general.part.html (original)
+++ subversion/site/publish/docs/community-guide/general.part.html Tue Nov 30 09:57:15 2010
@@ -634,10 +634,10 @@ change before being applied. Don't be d
not accepted immediately — it doesn't mean you goofed,
it just means that there are a <em>lot</em> of eyes looking at every
code submission, and it's a rare patch that doesn't have at least a
-little room for improvement. After reading 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>
+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>
<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