[svnbook] r3805 committed - * src/en/book/ch02-basic-usage.xml...
svnbook at googlecode.com
svnbook at googlecode.com
Fri Oct 15 13:21:40 CDT 2010
Revision: 3805
Author: cmpilato at gmail.com
Date: Fri Oct 15 11:16:49 2010
Log: * src/en/book/ch02-basic-usage.xml
Note that this chapter assumes you have a repos to work with, and
lose the bit that shows us creating one. While here, fix some
<indexterm> placement. (This takes care of the concern noted in
issue 66 ... or rather moves the concern elsewhere.)
http://code.google.com/p/svnbook/source/detail?r=3805
Modified:
/trunk/src/en/book/ch02-basic-usage.xml
=======================================
--- /trunk/src/en/book/ch02-basic-usage.xml Fri Oct 15 10:38:16 2010
+++ /trunk/src/en/book/ch02-basic-usage.xml Fri Oct 15 11:16:49 2010
@@ -19,7 +19,18 @@
model of Subversion. For a complete reference of all commands,
see <xref linkend="svn.ref"/>.</para>
- <para>Also, any Subversion operation that contacts the repository
+ <para>Also, this chapter assumes that the reader is seeking
+ information about how to interact in a basic fashion with an
+ existing Subversion repository. No repository means no working
+ copy; no working copy means not much of interest in this chapter.
+ There are many Internet sites which offer free or inexpensive
+ Subversion repository hosting services. Or, if you'd prefer to
+ set up and administer your own repositories, check out
+ <xref linkend="svn.reposadmin"/>. But don't expect the
+ examples in this chapter to work without the user having access
+ to a Subversion repository.</para>
+
+ <para>Finally, any Subversion operation that contacts the repository
over a network may potentially require that the user authenticate.
For the sake of simplicity, our examples throughout this chapter
avoid demonstrating and discussing authentication. Be aware that
@@ -151,13 +162,13 @@
<sect2 id="svn.tour.importing.import">
<title>Importing Files and Directories</title>
- <para>
- <indexterm>
- <primary>svn</primary>
- <secondary>subcommands</secondary>
- <tertiary>import</tertiary>
- </indexterm>
- The <command>svn import</command> command is a quick way to
+ <indexterm>
+ <primary>svn</primary>
+ <secondary>subcommands</secondary>
+ <tertiary>import</tertiary>
+ </indexterm>
+
+ <para>The <command>svn import</command> command is a quick way to
copy an unversioned tree of files into a repository, creating
intermediate directories as necessary. <command>svn
import</command> doesn't require a working copy, and your files
@@ -166,8 +177,8 @@
begin tracking in your Subversion repository. For example:</para>
<screen>
-$ svnadmin create /var/svn/repo
-$ svn import /path/to/mytree file:///var/svn/repo/some/project \
+$ svn import /path/to/mytree \
+ http://host.example.com/svn/repo/some/project \
-m "Initial import"
Adding mytree/foo.c
Adding mytree/bar.c
@@ -187,7 +198,7 @@
repository:</para>
<screen>
-$ svn list file:///var/svn/repo/some/project
+$ svn list http://host.example.com/svn/repo/some/project
bar.c
foo.c
subdir/
@@ -206,20 +217,20 @@
<sect2 id="svn.tour.importing.layout">
<title>Recommended Repository Layout</title>
- <para>
- <indexterm>
- <primary>trunk</primary>
- </indexterm>
- <indexterm>
- <primary>tags</primary>
- </indexterm>
- <indexterm>
- <primary>branches</primary>
- </indexterm>
- <indexterm>
- <primary>project root</primary>
- </indexterm>
- Subversion provides the ultimate flexibility in terms of
+ <indexterm>
+ <primary>trunk</primary>
+ </indexterm>
+ <indexterm>
+ <primary>tags</primary>
+ </indexterm>
+ <indexterm>
+ <primary>branches</primary>
+ </indexterm>
+ <indexterm>
+ <primary>project root</primary>
+ </indexterm>
+
+ <para>Subversion provides the ultimate flexibility in terms of
how you arrange your data. Because it simply versions
directories and files, and because it ascribes no particular
meaning to any of those objects, you may arrange the data in
More information about the svnbook-dev
mailing list