Re: Suggestions for handbook: Version Control with Subversion, Subversion 1.1

I think these edits would be *much* easier for the book maintainers to
digest if they were given in patch form. The svnbook.red-bean.com
website should have instructions for how to do that; you would use
'svn diff' to produce the patch.

-Karl

-- 
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
Mark Westenberger <m_west@routes.com> writes:
> Hello,
> 
> So, I'm a newbie, who started by blindly groping the elephant.
> 
> I've found this handbook to be one of the best I've come across.
> It is very well written!
> 
> If you wish, below I offer some dreadfully simple editorial
> notes coming from the uninitiated, virgin mind, naiive to
> what I was about to read and expecting a struggle to comprehend.
> (It wasn't after all).
> They may assist the next round of "men of Indostan".
> 
> There is one edit with a [<set of choices for you>] which I am
> yet to discover for myself!
> 
> After a mere day and a half, I've got a server up and running
> with our project stuffed into SVN, and with some smiles, have
> made the first round of new (bug?) contributions to our code.
> 
> Kind regards,
> Mark Westenberger
> 
> ----------------------------------------------------------
> Subversion's Components
> 
> svn
> The client-side command-line interface.
> 
> svnversion
> A client-side program for reporting ...
> 
> svnlook
> An administrative, server-side tool for inspecting ...
> 
> svnadmin
> An administrative, server-side tool for creating...
> 
> svndumpfilter
> An administrative, server-side program for filtering ...
> 
> mod_dav_svn
> <as is>
> 
> svnserve
> The SVN server-side workhorse. A custom standalone ...
> ----------------------------------------------------------
> A Quick Start
> 
> If you're one of those folks who prefers to learn by experimentation,
> the following demonstration will get
> you up and running, with a small "Hello World"-sized example complete
> with the single SVN repository.
> 
> ...
> 
> Subversion stores all versioned data in a single central
> repository. To begin, create that single new repository:
> 
> ...
> 
> This command creates a new directory /path/to/repos which contains a
> Subversion repository. Note that
> in this case a path is used and not a URL.  This is because svnadmin
> is used on the server-side. Elaborations
> on this difference are presented in the section entitled "Repository
> Creation and Configuration".
> 
> ...
> your structure should contain three top-level directories named branches,
> tags, and trunk. The names "branches", "tags" and "trunk" are
> [reserved? | special? | just suggestions?].
> Further examples will expect this structure, so don't be skimpy on
> space by cutting it back.  Here is the tree you should create:
> 
> ...
> 
> At this point, you have the option of making your new repository
> available to others over a network as the
> single, central SVN repository. This would expect that the computer on
> which you are performing these
> examples could act as a server within your specific network.
> ----------------------------------------------------------
> Creating a Branch
> 
> There are two different ways to make a copy. We'll demonstrate the
> messy way first, just to make the concept clear.
> You will start from the root directory, and not "trunk" as we need the
> subdirectories in the next steps.
> So, to begin, check out a working copy of the project's root
> directory, /calc:
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 
-- 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org