Author: danielsh
Date: Wed Sep 29 13:40:53 2010
New Revision: 1002624
URL: http://svn.apache.org/viewvc?rev=1002624&view=rev
Log:
* /site/publish/docs/community-guide/issues.part.html,
/site/publish/docs/community-guide/mailing-lists.part.html:
Fix a couple of broken links.
Modified:
subversion/site/publish/docs/community-guide/issues.part.html
subversion/site/publish/docs/community-guide/mailing-lists.part.html
Modified: subversion/site/publish/docs/community-guide/issues.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/issues.part.html?rev=1002624&r1=1002623&r2=1002624&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/issues.part.html (original)
+++ subversion/site/publish/docs/community-guide/issues.part.html Wed Sep 29
13:40:53 2010
@@ -132,7 +132,7 @@ obvious to someone else, so it's best to
Follow that with the environment description, and the reproduction
recipe. If you also want to include speculation as to the cause, and
even a patch to fix the bug, that's great — see the <a
-href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#patches">patch submission
guidelines</a>.</p>
+href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#patches">patch submission
guidelines</a>.</p>
<p>Post all of this information to <a
href="mailto:[email protected]";
Modified: subversion/site/publish/docs/community-guide/mailing-lists.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/mailing-lists.part.html?rev=1002624&r1=1002623&r2=1002624&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/mailing-lists.part.html
(original)
+++ subversion/site/publish/docs/community-guide/mailing-lists.part.html Wed
Sep 29 13:40:53 2010
@@ -42,7 +42,7 @@ unfortunate, but it does not make the qu
<p>Of course, if the mail is about a possible bug in Subversion, and
got no reaction on users@, then asking on dev@ is
fine — bugs are a development topic.
-And <a href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#patches" >patches</a>
should always be sent directly to
+And <a href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#sending-patches"
>patches</a> should always be sent directly to
d...@.</p>
</div> <!-- where-to-post -->
@@ -85,7 +85,7 @@ diverge.</p>
columns, you leave room for quoting characters to be added in future
replies without forcing a rewrapping of the text. The 72-column limit
only applies to the prose part of your message, of course. If you're
-posting a patch, see <a href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE"
-->#patches">the section on
+posting a patch, see <a href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE"
-->#sending-patches">the section on
patches</a>.</p>
<p>Some mailers do a kind of automatic line-wrapping, whereby when
