> Mine uses Subversions WebDAV as is.
What is subversions WebDAV interface like to work with?
>> * Atomic file system operations through journaling.
> I've no server side beyond Subversion.
The journaling system was mostly needed on the client. During a
'checkout' any file being placed in the lo
> * HTTP(S) based sync protocol.
Mine uses Subversions WebDAV as is.
> * All files, both on the client and the server, are stored as plain files
with there original names.
Mine too, or plain binary 'as is'
> * Stores limited version history on the server only. Has limited support
for file versi
@Ryan Schmidt @Stefan Sperling. I guess that the difficulty of
implementing this depends on how much of the client code depends on
the existence of those files. From the linked bug tracker item, the
answer appears to be 'quite a lot', though I don't know anything about
this codebase.
@Paul Hammant
>
> As I have not used SVN for several years I realize that this feature
> may have been added. If not has it been considered?
I have a file-sync agent that uses a non-standard Subversion install as a
backing-store over WebDAV. It only keeps one copy on the client side, and
will shuttle all saves
On Wed, Sep 27, 2017 at 06:01:33AM -0500, Ryan Schmidt wrote:
>
> On Sep 26, 2017, at 13:13, Robert Hickman wrote:
>
> > I tend to work on projects with a large amount of binary data along
> > with source code and need to track them together. To this date
> > Subversion is the only tool that I've
On Sep 26, 2017, at 13:13, Robert Hickman wrote:
> I tend to work on projects with a large amount of binary data along
> with source code and need to track them together. To this date
> Subversion is the only tool that I've used which handles this
> dependably. That being said I have one major is
