You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by cm...@apache.org on 2010/08/25 21:40:52 UTC
svn commit: r989320 - in /subversion/site/publish/docs/community-guide:
general.part.html roles.part.html
Author: cmpilato
Date: Wed Aug 25 19:40:52 2010
New Revision: 989320
URL: http://svn.apache.org/viewvc?rev=989320&view=rev
Log:
Fix some broken links in the Community Guide.
* site/publish/docs/community-guide/general.part.html,
* site/publish/docs/community-guide/roles.part.html
Fix links to "Writing log messages" section.
Patch by: anatoly t. <techtonik{__AT__}gmail.com>
Modified:
subversion/site/publish/docs/community-guide/general.part.html
subversion/site/publish/docs/community-guide/roles.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=989320&r1=989319&r2=989320&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/general.part.html (original)
+++ subversion/site/publish/docs/community-guide/general.part.html Wed Aug 25 19:40:52 2010
@@ -590,7 +590,7 @@ helps potential reviewers understand the
increases the likelihood that it will be applied. You can put the log
message in the body of the email, or at the top of the patch
attachment (see below). Either way, it should follow the guidelines
-given in <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#log-messages">Writing log messages</a>, and be
+given in <a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#log-messages">Writing log messages</a>, and be
enclosed in triple square brackets, like so:</p>
<pre>
@@ -627,7 +627,7 @@ the bug in detail and give a reproductio
these guidelines is when the patch addresses a specific issue in the
issues database — in that case, just refer to the
issue number in your log message, as described
-in <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#log-messages">Writing log messages</a>.</p>
+in <a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#log-messages">Writing log messages</a>.</p>
<p>It is normal for patches to undergo several rounds of feedback and
change before being applied. Don't be discouraged if your patch is
Modified: subversion/site/publish/docs/community-guide/roles.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/roles.part.html?rev=989320&r1=989319&r2=989320&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/roles.part.html (original)
+++ subversion/site/publish/docs/community-guide/roles.part.html Wed Aug 25 19:40:52 2010
@@ -154,7 +154,7 @@ comments, commit messages, etc. We rely
to determine what is "obvious"; if you're not sure, just ask.</p>
<p>Whenever you invoke the "obvious fix" rule, please say so in
-the <a href="<!--#echo var="GUIDE_ROLES_PAGE" -->#log-messages">log message</a> of your commit. For example:</p>
+the <a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#log-messages">log message</a> of your commit. For example:</p>
<pre>
------------------------------------------------------------------------