On Jan 17, 2005, at 11:24 AM, Dassi, Nasser wrote:
>
>
> Hello everybody, here is my next challenge which needs clarification
> (even after re-reading the entire SVN Book).
>
> Background:
> Apache2, SVN 1.1.x, mod_dav_svn, SVNAutoversioning, and 2 sites exist
> (port 80 is classic apache http, and port 81 is webdav+svn configured)
> pointing to same location/directory.
>
> Situtation + Results:
> SVN Working Copy (via http URL) edits with 'DAV on' updates the WC
> files on-the-fly without versioning automatically. But...
> SVN Working Copy (via same http URL) edits with 'DAV svn'
> autoversions the repository on-the-fly but *does not* update the
> working copy files.
>
> Question:
> Is this by design? Is it possible to 'auto-update' the working copy
> files *and* the repository when Autoversioning is used?
>
> This may be a 'bug' for the autoversioning module, unless if
> by-design; but it seems awkward and annoying to have a remote server
> requiring manual intervention to view HTML change updates just because
> SVN is used to auto-version files.
>
>
I honestly don't understand.. What do you mean by "auto-update"?
You've given us a description of two different server configurations,
but I can't decipher what commands you're running and what results
you're seeing. Can you try re-explaining in a different way, being as
specific as possible?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 17 19:30:53 2005