latest svn book?

C. Michael Pilato cmpilato at
Fri Jul 21 22:26:04 CDT 2017


Thanks for the comments and suggestions about the book.  It's true that
activity on the English text has slowed to a near halt. Of the three
original authors, I alone maintain ties with the project these days, and
time is simply not been available for upkeep of the work. But it is an open
source project, so quality contributions are always welcome, and I'm happy
to review patches.

Of course, the mailing list is the primary avenue for such to take place,
so it's unfortunate that you've not been successful at subscribing it.
Have you tried doing so via or did you use some
other approach? Our server got a major OS upgrade recently, so it is
possible that something broke in the process. If that's the case, I'd
appreciate the chance to work out those wrinkles with your assistance.

-- Mike

On Jul 21, 2017 4:43 PM, "Daniel Shahaf" <d.s at> wrote:

svnbook-dev@, the following feedback about the book was sent to users@ :

Nathan Hartman wrote on Fri, 21 Jul 2017 16:12 -0400:
> On Thu, Jul 20, 2017 at 6:03 AM, Daniel Shahaf <d.s at>
> wrote:
> > Todd Armstrong wrote on Wed, 19 Jul 2017 19:22 +0000:
> > > There’s a 1.8 draft in the nightly build section of that page with a
> > 2016 copyright that I’ve been using.
> > >
> > > It’s not available in PDF form yet, though.
> >
> > Requests for a PDF version should be addressed to the book's mailing
> > list (svnbook-dev at
> >
> I tried on two occasions to subscribe to that mailing list but there
> to be no response. Does anyone know why or have contact with the book
> maintainers? It's a very good book. I still refer to it frequently.
> Bringing it up-to-date with 1.9 and current best practices would benefit
> all of us.
> Also, some sections could be expanded. Just one example is how to deal
> vendor branches. There was some recent discussion here about communication
> between the FreeBSD and Subversion maintainers, and some practices that
> could be updated by FreeBSD and/or improvements made to Subversion. The
> results of such discussions are exactly the sort of information that
> be documented in the svn-book. I propose an additional chapter on real
> world scenarios and case studies, to help potential adopters and long-time
> users alike.

svnbook-dev mailing list
svnbook-dev at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the svnbook-dev mailing list