[svnbook commit] r3084 - trunk/src/en/book
sussman
noreply at red-bean.com
Fri May 23 16:38:07 CDT 2008
Author: sussman
Date: Fri May 23 16:38:07 2008
New Revision: 3084
Log:
* appa-quickstart.xml: put in O'Reilly copyedits.
Modified:
trunk/src/en/book/appa-quickstart.xml
Modified: trunk/src/en/book/appa-quickstart.xml
==============================================================================
--- trunk/src/en/book/appa-quickstart.xml (original)
+++ trunk/src/en/book/appa-quickstart.xml Fri May 23 16:38:07 2008
@@ -76,11 +76,11 @@
once you do, you can check out a working copy of the Subversion source
repository from <ulink url="http://svn.collab.net/repos/svn/trunk/"/>:
<footnote>
- <para>Note that the URL checked out in the example above
- ends not with <literal>svn</literal>, but with a
- subdirectory thereof called <literal>trunk</literal>. See
- our discussion of Subversion's branching and tagging model
- for the reasoning behind this.</para>
+ <para>Note that the URL checked out in the example ends not
+ with <literal>svn</literal>, but with a subdirectory thereof
+ called <literal>trunk</literal>. See our discussion of
+ Subversion's branching and tagging model for the reasoning
+ behind this.</para>
</footnote>
</para>
@@ -94,15 +94,15 @@
…
</screen>
- <para>The above command will create a working copy of the latest
- (unreleased) Subversion source code into a subdirectory
+ <para>The preceding command will create a working copy of the
+ latest (unreleased) Subversion source code into a subdirectory
named <filename>subversion</filename> in your current working
directory. You can adjust that last argument as you see fit.
Regardless of what you call the new working copy directory,
though, after this operation completes, you will now have the
Subversion source code. Of course, you will still need to fetch
- a few helper libraries (apr, apr-util, etc.)—see
- the <filename>INSTALL</filename> file in the top level of the
+ a few helper libraries (apr, apr-util, etc.)—see the
+ <filename>INSTALL</filename> file in the top level of the
working copy for details.</para>
</sect1>
@@ -116,9 +116,9 @@
<blockquote>
<para><quote>Please make sure your seat backs are in their full,
- upright position, and that your tray tables are stored.
- Flight attendants, prepare for take-off….</quote></para>
- </blockquote>
+ upright position and that your tray tables are stored. Flight
+ attendants, prepare for take-off….</quote></para>
+ </blockquote>
<para>What follows is a quick tutorial that walks you through some
basic Subversion configuration and operation. When you finish
@@ -145,42 +145,40 @@
conf/ dav/ db/ format hooks/ locks/ README.txt
</screen>
- <para>This command creates a new directory
- <filename>/var/svn/repos</filename> which contains a Subversion
+ <para>This command creates a new directory,
+ <filename>/var/svn/repos</filename>, which contains a Subversion
repository. This new directory contains (among other things) a
collection of database files. You won't see your versioned
files if you peek inside. For more information about repository
- creation and maintenance, see
- <xref linkend="svn.reposadmin"/>.</para>
+ creation and maintenance, see <xref
+ linkend="svn.reposadmin"/>.</para>
- <para>Subversion has no concept of a <quote>project</quote>. The
+ <para>Subversion has no concept of a <quote>project.</quote> The
repository is just a virtual versioned filesystem, a large tree
that can hold anything you wish. Some administrators prefer to
store only one project in a repository, and others prefer to
store multiple projects in a repository by placing them into
separate directories. The merits of each approach are discussed
in <xref linkend="svn.reposadmin.projects.chooselayout"/>.
- Either way, the repository only manages files and directories,
- so it's up to humans to interpret particular directories
- as <quote>projects</quote>. So while you might see references
- to projects throughout this book, keep in mind that we're only
- ever talking about some directory (or collection of directories)
- in the repository.</para>
+ Either way, the repository manages only files and directories,
+ so it's up to humans to interpret particular directories as
+ <quote>projects</quote>. So while you might see references to
+ projects throughout this book, keep in mind that we're only ever
+ talking about some directory (or collection of directories) in
+ the repository.</para>
<para>In this example, we assume that you already have some sort
of project (a collection of files and directories) that you wish
to import into your newly created Subversion repository. Begin
- by organizing your data into a single directory
- called <filename>myproject</filename> (or whatever you wish).
- For reasons that will be clear later (see
- <xref linkend="svn.branchmerge"/>), your project's tree
- structure should contain three top-level directories
- named <filename>branches</filename>,
- <filename>tags</filename>, and
- <filename>trunk</filename>. The <filename>trunk</filename>
- directory should contain all of your data,
- while <filename>branches</filename>
- and <filename>tags</filename> directories are empty:</para>
+ by organizing your data into a single directory called
+ <filename>myproject</filename> (or whatever you wish). For
+ reasons explained in <xref linkend="svn.branchmerge"/>, your
+ project's tree structure should contain three top-level
+ directories named <filename>branches</filename>,
+ <filename>tags</filename>, and <filename>trunk</filename>. The
+ <filename>trunk</filename> directory should contain all of your
+ data, while the <filename>branches</filename> and
+ <filename>tags</filename> directories are empty:</para>
<screen>
/tmp/myproject/branches/
@@ -259,7 +257,7 @@
</listitem>
<listitem>
<para>Run <command>svn update</command> to bring your working
- copy <quote>up-to-date</quote> with the repository.</para>
+ copy <quote>up to date</quote> with the repository.</para>
</listitem>
</itemizedlist>
More information about the svnbook-dev
mailing list