On Jun 25, 2005, at 2:48 AM, Norbert Unterberg wrote:
> * When creating a word document (MS Word 2000) using the integrated
> client (File --> save as ... --> http://path/to/repos/test.doc) the
> file is saved without problems. But the file is not marked as binary
> as it would have when adding with the command line client.
Correct, that's strictly a subversion client feature. WebDAV clients
have no idea about binary vs. text. They don't care, and they don't
try to deduce like the svn client does. There *is* a standard DAV
property for representing mime-type (DAV:getcontenttype), but I've
never seen a DAV client automatically set it the way the svn client
tries to automatically set the svn:mime-type property.
> * When getting a text file via WebDav, no keyword expansion or CRLF
> conversion is done. That means that a text file with svn:eol-style =
> native gets unix line endings on windows.
Again, keyword expansion and EOL conversion are concepts that only
exist in version control systems, not generic WebDAV, which is
nothing more than a dumb file-sharing protocol. Keyword expansion
and EOL conversions are features exclusive to subversion clients.
(The subversion server has nothing to do with data-munging, and never
has. It stores exactly what it's given, and returns it later byte-
> * When editing that text file on windows it might get a mixture of LF
> and CRLF endings. What happens to the line endings when I put it back
> into the repos using WebDav?
DAV is just dumb file-sharing protocol over HTTP. No examination of
file contents is going on. Your question is equivalent to asking,
"what happens to line endings if I write the file to an NFS share?"
Nothing at all. The server never munges data. All of the data-
munging features you're looking for are entirely subversion-client
> Does it get corrupt or is the "damage"
> repaired on the next checkout?
Corruption is corruption, there's nothing available to notice or
repair file contents.
Caveat emptor... which means, "we hope you like it!" :-)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Jun 25 15:56:24 2005