subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r900996 - in /subversion/site/publish/docs: community-guide/ community-guide/index.html hacking/
Date Tue, 19 Jan 2010 22:58:08 GMT
Author: cmpilato
Date: Tue Jan 19 22:58:07 2010
New Revision: 900996

* site/publish/docs/hacking
  Rename "The Hacker's Guide to Subversion"...

* site/publish/docs/community-guide the "Subversion Community Guide".

* site/publish/docs/community-guide/index.html
  Note the new name and title of this document, and its intended
  audience.  Also, remove the self-naming portions of <a> targets.

      - copied from r900994, subversion/site/publish/docs/hacking/

Modified: subversion/site/publish/docs/community-guide/index.html
--- subversion/site/publish/docs/community-guide/index.html (original)
+++ subversion/site/publish/docs/community-guide/index.html Tue Jan 19 22:58:07 2010
@@ -3,7 +3,7 @@
 <html xmlns="">
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<title>Hacker's Guide to Subversion</title>
+<title>Subversion Community Guide</title>
 <style type="text/css" media="screen">
 body {
   font-family: serif;
@@ -27,10 +27,10 @@
-<h1>Hacker's Guide to Subversion</h1>
+<h1>Subversion Community Guide</h1>
-<p>If you are contributing code to the Subversion project, please read
-this first.</p>
+<p>If you are contributing to the Subversion project, please read this
 <!-- Other pages seem to use "h2" for ToC, but I think "h1" works
      better, because the ToC is fundamentally different from other
@@ -3065,7 +3065,7 @@
 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&nbsp;&mdash;&nbsp;see <a
-href="hacking.html#patches">hacking.html#patches</a> for instructions
+href="#patches">#patches</a> for instructions
 on sending patches.</p>
 <p>Post all of this information to <a
@@ -3845,7 +3845,7 @@
 <p>The protocol used to accept or refuse the merging of changes from
 trunk is of interest to all Subversion developers, and as such is
-documented in <a href="hacking.html#release-stabilization">the
+documented in <a href="#release-stabilization">the
 release stabilization section of the hacking guide</a>.</p>
 </div> <!-- porting-changes -->
@@ -3908,7 +3908,7 @@
 <div class="h3" id="adding-changes">
 <h3>Adding content for patch release</h3>
-<p>As part of <a href="/hacking.html#release-stabilization">release
+<p>As part of <a href="#release-stabilization">release
 stabilization</a>, <tt>CHANGES</tt> should be updated as bug fixes are
 ported to the release branch.  Generally, if you merge a revision or group
 of revisions (i.e., an item in <tt>STATUS</tt>) to the release branch, you
@@ -4353,7 +4353,7 @@
 <p>Steps (2) and (3) generate a Makefile; step (4) generates
-<p>The Subversion project has <a href="hacking.html#other-conventions">a
+<p>The Subversion project has <a href="#other-conventions">a
 policy</a> not to put names in its files, so please apply the two changes
 described below.</p>
@@ -4589,7 +4589,7 @@
 <p>The project has standardised the use of quotes.  Some translation
 teams have done the same.  If there is no translation team for your
 locale or they did not standardise quoting, please follow the project
-guidelines per www/hacking.html.  If they did: follow them :-)</p>
+guidelines elsewhere in this guide.  If they did: follow them :-)</p>
 </div>  <!-- quotes -->

View raw message