Slapping your colleagues around is not a good solution :)
If a repository out of your control, there is not a good solution for
this on osX that I'm aware of. I'm hoping someone will find one.
I work around it by mounting a linux filesystem via nfs, and checking
out onto that volume. I work on we
Another (perhaps simpler) way to do this is to use the package installers at
http://www.collab.net/downloads/community/ instead. The binaries will be
installed in /opt/subversion so they don't collide with the built-in SVN 1.4.4
tool set.
Alternatively, you can make Versions use SVN 1.4 interna
I solved this by installing subversion 1.6.5 via http://www.macports.org/
On Jan 3, 8:22 am, Jean-Rubin L wrote:
> Hi,
> I am using Versions but I'm using BBedit to edit my files. I'd like to
> commit from BBedit but when I try to do so it says the version of
> subversion is too old. Long story s
This is probably because HFS+ (the default file system for OS X) is
case-preserving, but not case-sensitive. This means that filenames that differ
only in capitalization are considered to be the same. Although this works on
Linux, it is poor practice to name files this way, not only because deve
Hey,
I have a problem and have diagnosed it as a name conflict. However,
this appears to be working fine for the developers that use Linux. The
problem is as follows. There are a number of instances in the
application where there are near identical filenames. For example.
swfupload.js
Swfupload.j
