[scponly] subversion support

[Dimitri Papadopoulos-Orfanos]

Hi,

> Our users aren't ssh'ing into the computer that is running subversion.  They 
> have checkouts on a webserver that they only have scponly access to.  Thus, 
> they can use sftp to modify the files, and then use ssh user at host svn ci -m 
> "blah blah" /path/... to commit the files.  Or, ssh user at host svn 
> update /path/....  Even though they could commit directly to the repository, 
> they wouldn't have a good way to update the web server with access to the svn 
> command on the server.
> [...]
> The default should be whatever most people have need of.  For us, we need to 
> use the svn command.  Recently, a couple of people have posted about 
> svnserve.  Apparently svn use was needed first... if that's indicative of the 
> need???

Please don't take this as a critic, you certainly have good reasons to 
use Subversion this way, but it's the first time I hear of such a 
complicated way of using Subversion. The book, the Web site, all of them 
refer to svn+ssh.

Dimitri Papadopoulos