So where did this idea about “… working copies on systems such as Windows that
do not support symlinks” come from? NTFS supports symlinks, and has supported
it for many years. If my memory is correct, it wasn’t avialable in the CLI
interface, cmd.exe, utntil long after the file system API provid
Maybe unrelated to your problem, but worth checking up anyway:
We had lots of problems with SlikSVN until we discovered that some users had
selected that SVN client because it offered a user interface in their native
language, including translations of those error messages parsed by SVN. Once
t
I had exactly the same problem today.
The message occurs when I press the OK button in the commit dialog box.
Most of my changes were restructuring of a moderately sized directory,
but some of those renames had been unsuccessful (e.g. due to misspelling
where the new name already existed).
I t
We are using the CodeCollaborator system from SmartBear for code reviews. This
system uses the command: svn -r "firstversion:lastversion" svnpath
to generate a diff list used indicate which lines were modified for the code
revision in question.
Problem is with files that have been moved/renamed
