Reviewers: dev_subversion.apache.org,

Message:
Community guide contains broken links to Writing log messages chapter.
Please, review this patch.

--
anatoly t.

Description:
* publish\docs\community-guide\general.part.html,
  publish\docs\community-guide\roles.part.html:
  Fix links to "Writing log messages" chapter


Please review this at http://codereview.appspot.com/2016045/

Affected files:
  M     publish/docs/community-guide/general.part.html
  M     publish/docs/community-guide/roles.part.html


Index: publish/docs/community-guide/general.part.html
===================================================================
--- publish/docs/community-guide/general.part.html      (revision 989171)
+++ publish/docs/community-guide/general.part.html      (working copy)
@@ -590,7 +590,7 @@
 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 @@
 these guidelines is when the patch addresses a specific issue in the
 issues database&nbsp;&mdash; 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
Index: publish/docs/community-guide/roles.part.html
===================================================================
--- publish/docs/community-guide/roles.part.html        (revision 989171)
+++ publish/docs/community-guide/roles.part.html        (working copy)
@@ -154,7 +154,7 @@
 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>
 ------------------------------------------------------------------------


Reply via email to