 |
 |
Free Books / Computers / Subversion / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
Invoking the Server |
|
||
|
||||
|
|
|
||
|
||||
|
|
Free Books / Computers / Subversion / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
Invoking the Server |
|
||
|
||||
|
|
|
||
|
||||
This section is from the "Version Control with Subversion" book, by Ben Collins-Sussman, Brian W. Fitzpatrick and C. Michael Pilato. Also available from Amazon: Version Control with Subversion.
There are a few different ways to run the svnserve program:
Run svnserve as a standalone daemon, listening for requests.
Have the Unix inetd daemon temporarily spawn svnserve whenever a request comes in on a certain port.
Have SSH invoke a temporary svnserve over an encrypted tunnel.
Run svnserve as a Microsoft Windows service.
subversion, svn, revision control, backup, review, revert, merge, commit, update, branch, changes, collision
|
|
|
|
 |
|