Peter Davis <peter@pdavis.cx> writes:
> I had no idea you had been writing such an excellent piece of
> documentation! Other projects would be proud to have such a
> handbook.
Sir, you make my head swell. :-)
> * In section 3.5, you talk about writing a Perl script to crypt(3) passwords
> for Apache's access control. I find it much easier to use the htpasswd
> command that is installed in /path/to/apache/bin/htpasswd:
>
> $ /path/to/apache/bin/htpasswd /path/to/passwd/file username
> New password: [password]
> Re-type new password: [password]
> Adding password for user username
>
> Hopefully this would be a little less intimidating to non-Perl users.
Oh wow, great idea. I totally forgot about htpasswd. I definitely
swap that in instead of the perl script.
> * Of course I personally know all about branches and tags (Section
> 2.4) and their use-cases, since they are such an integral part of
> most version control systems, but newbies may not. If you don't
> want to spend time reproducing what many others have already written
> (or maybe this handbook is just not aimed at total newbies?),
Actually, I'd like to think that "total newbies to version control"
can still understand this document... although I suppose the document
*does* assume that you are a basic Unix-user.
I'll see if I can fill this hole with a link or explanation...
> * What happened to the 'http://foo/svn/.../@rev' syntax? Did that get
> removed? I thought it was kind of nice :)
No, it's still around, but '-r N' is easier to introduce. I figure
the URL@N syntax can be discovered later on when people run "svn help
diff" or "svn help merge".
> In any case, an explaination of how URL's work with Subversion
> (both http:// and file://), especially how the left hand part
> specifies the path to the repository and the right hand part is the
> node within the repository, but the division between the two is not
> usually apparent. Maybe this is obvious.
No, maybe it isn't actually... that's a good point!
> On a related note, in your first example of using 'svnadmin create
> myrepos', it isn't clear what exactly 'myrepos' is supposed to be.
> It is a directory of course, but it might be helpful to show the
> example (and other examples using 'myrepos') using a full path like
> '/path/to/myrepos', just to show that myrepos is actually created as
> a directory on the disk, and is not just some magical identifier.
> Also consider pointing out that '/path/to' has to exist beforehand.
Ah, yes, sure.
Thanks for the feedback!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 18 04:46:27 2002