[svnbook] r4375 committed - * en/book/ch04-branching-and-merging.xml...

svnbook at googlecode.com svnbook at googlecode.com
Tue Jan 29 13:03:16 CST 2013


Revision: 4375
Author:   cmpilato at gmail.com
Date:     Tue Jan 29 10:59:53 2013
Log:      * en/book/ch04-branching-and-merging.xml
   (svn.branchmerge.maint.layout): Minor wording tweaks for clarity
     regarding repository layouts.
http://code.google.com/p/svnbook/source/detail?r=4375

Modified:
  /trunk/en/book/ch04-branching-and-merging.xml

=======================================
--- /trunk/en/book/ch04-branching-and-merging.xml	Tue Jan 29 10:10:34 2013
+++ /trunk/en/book/ch04-branching-and-merging.xml	Tue Jan 29 10:59:53 2013
@@ -3329,13 +3329,14 @@
      <sect2 id="svn.branchmerge.maint.layout">
        <title>Repository Layout</title>

-      <para>There are some standard, recommended ways to organize a
-        repository.  Most people create a <filename>trunk</filename>
-        directory to hold the <quote>main line</quote> of development,
-        a <filename>branches</filename> directory to contain branch
-        copies, and a <filename>tags</filename> directory to contain
-        tag copies.  If a repository holds only one project,
-        often people create these top-level directories:</para>
+      <para>There are some standard, recommended ways to organize the
+        contents of a repository.  Most people create a
+        <filename>trunk</filename> directory to hold the <quote>main
+        line</quote> of development, a <filename>branches</filename>
+        directory to contain branch copies, and
+        a <filename>tags</filename> directory to contain tag copies.
+        If a repository holds only one project, often people create
+        these top-level directories:</para>

        <informalexample>
          <literallayout>




More information about the svnbook-dev mailing list