Re: rapidsvn feedback

Karl Fogel <kfogel@newton.ch.collab.net> writes:
> A brief rant:
>
> The challenge in writing documentation is deciding what not to
> include. Technical books typically run *over*, not under, their
> projected page count. If we're not careful, we'll have an enormous
> doorstop in which casual browsing is punished by acres of off-topic or
> redundant material. (Sound familiar? Sound like a lot of technical
> books you've seen? :-) ).
>
> Good SCM practices are completely independent of Subversion. You can
> use SVN without good practices. You can have good practices and yet
> not be using SVN.
>
> Let's please keep non-Subversion material out of the handbook.

I am in complete agreement with Karl on this (There's a first time for
everything). :)

If you really like the coding practices (I for one love them!) as
described in

   http://svn.collab.net/repos/svn/trunk/HACKING

Then perhaps you could use that as a starting point for a "Good Coding
Practices Handbook" somewhere, but it shouldn't be in the Subversion
Handbook.

-Fitz

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 16:55:01 2002