Hello,
I've upgraded to the latest version of the versions software (1.0.5)
yesterday and I seem to get a lot of Connection closed
unexpectedly errors (which I didn't get before).
I can connect after trying long enough but the software doesn't seem
to be very stable.
Is there a way to find out
... I had no previous problems running versions until I restarted my
computer today (OSX 10.5.8). When I did I started receiving 'Oops,
Versions hit a bumb in the road! Versions has envountered a problem.
Please send us the anonymous crash report to help us fix the problem.'
and I can no longer
You could try and see if backing up and trashing your Versions
preference file fixes the issue.
Regards,
--
Jasper
the versions team
On Sep 10, 8:45 pm, Gabriel Gilder gabriel.gil...@gmail.com wrote:
Awesome, glad to hear these are in the works.
I took a look at the column widths again on
Hi Jeff,
Could you please take a look in the Console application (located in
Applications/Utilities/) to see if you can find any references to
Versions? And then send those us those reports to our support email
address (versi...@madebysofa.com).
Regards,
--
Jasper
the versions team
On Sep 10,
Hi Stijn,
Could you please take a look in the Console application (located in
Applications/Utilities/ ) and see if you can find any references to
Versions and ssh authorizations?
Regards,
--
Jasper
the versions team
On Sep 10, 4:22 pm, stikkos stik...@gmail.com wrote:
Hello,
I've upgraded to
Even thought the newer tools may be installed, when you specify only
svn in Terminal, it uses the first matching executable it finds,
which is /usr/bin/svn on Leopard. If you want to use a newer version
on Leopard, the simplest way is to specify the full path to the
executable
For those of you who have Word files under Version control, this might
be of interest,
I've just whipped up a little comparison script that tries to use
Word's native comparison features when you're trying to compare
difference on a Word file from Versions. This will most likely only
work woth
Quite a while ago, when we first shipped Versions with SVN 1.5
support, I made a little postflight script for the CollabNet SVN
installers for Mac OS X that adds the newly installed command line
tools to your path variable automatically, for a bunch of different
shells.
For mysterious reasons it
