At 12:03 AM 8/17/2007, Ryan Schmidt wrote:
>On Aug 16, 2007, at 17:31, Tigran wrote:
>>This is for windows environment.
>>I'd like to setup subversion on a server where users access files
>>via windows share drive. On the server itself I am able to commit
>>changes but I can't commit changes from another system. The server
>>where subversion is installed notices the change in the file and
>>icon on the file changes but I can't commit changes.
>>Well I know why I can't commit changes its because I need
>>subversion client running on the system doing the changes. I also
>>need subversion server running on the server. But before we get to
>>that. I would prefer an autocommit with no client software. That
>>way any changes made to the files on the server get automatically
>>committed. Problem is where I read about autocommit it talks about
>>WebDAV and I don't want to have a WebDAV server. So is this
>>possible without WebDAV? If it is possible will adding new files
>>also work or is autocommit strictly commit and adding new files
>>will have to be done with another process?
>>If the autocommit without WebDAV is not possible my second options
>>is to run the subversion server and client. Does anybody have quick
>>instrstructions on how to do this?
>I wasn't clear or whether you're talking about a working copy on a
>share drive or a repository on a share drive. It's recommended you do
>neither. Repository on anything but a local drive is often quite
>problematic. Working copy on a share drive can work, though you may
>run into some issues.
>But that's neither here nor there since what you ultimately want is
>the auto-versioning feature. No, there is no way to do it other than
>running an Apache2/WebDAV server. Instructions for setting up
>Subversion in this or any other configuration are in the book, which
>you should read:
That answered my question thank you very much.
And many thanks to all the people working on this great program.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Aug 17 23:32:25 2007