> On 2019-03-01 11:53, Stefan Sperling wrote:
> Hi Denis,
> This problem is not specific to symbolic links.
> There are quite a few cases where --xml produces invalid XML
> when it runs into some kind of error. Perhaps the command
> line client should be fixed to close open XML tags when an
> error occurs, though this also risks people or scripts not
> noticing such errors.
Thanks, but let's me explain it otherwise:
I have access to the source tree of some development project that is
*not* under any version control system. I would like to build a
minimal level of versioning by committing this source tree into
Subversion at regular intervals, e.g. each day (automatically).
What would be the best strategy? I can figure out this one:
1) Within the working copy, delete the existing tree (not svn delete)
2) Extract the new tree at the same place
3) Interpret the result of 'svn status' in terms of 'svn add' and
'svn delete' to apply on the working copy (details omitted here)
The difficulty is to make sure that all peculiarities of a file system
changes (say: only files, folders and symlinks) are handled properly.
I don't talk about I/O errors of course.
Received on 2019-03-02 10:17:02 CET