On Apr 28, 5:50 pm, Ray raimondi...@gmail.com wrote:
I've never seen this happen. What you describe is pretty basic use of SVN,
so I suspect something else is at play here. Versions successfully updates
my working copies.
When you did this, did you check what was going on with svn from the
On May 5, 1:44 am, Cue qbiz...@googlemail.com wrote:
On Apr 28, 5:50 pm, Ray raimondi...@gmail.com wrote:
I've never seen this happen. What you describe is pretty basic use of SVN,
so I suspect something else is at play here. Versions successfully updates
my working copies.
When you
An update tells me there's nothing to update and that I'm at the
latest revision. The issue is not svn, nor the method carried out to
resolve a conflict. The issue begs the question why Versions doesn't
mark the file as clean, it just sits there to assume the file has been
modified yet
Versions isn't all that great. After resolving a conflict, committing,
the file still has the exclamation icon overlay which marks it as
modified... What is going on?
SynchroSVN is an ugly app, but it works as its supposed to.
Unfortunately I've now had to revert back to that. Thankfully I was
On Wed, Apr 28, 2010 at 11:20 AM, Cue qbiz...@googlemail.com wrote:
Versions isn't all that great. After resolving a conflict, committing,
the file still has the exclamation icon overlay which marks it as
modified... What is going on?
I've never seen this happen. What you describe is pretty
I have a working copy checkout on MAC1 and MAC2.
MAC1 deletes a file, commits.
MAC2 updates, the file is deleted from the disk (it doesn't exist! how
it should be!)... but in Versions it STILL appears as an unversioned
file.
The pros: The file doesn't actually exist when committing or nothing
