> But it's perfectly clear from the dialog itself. There's a button
> Repository", if you click on it, then an 'svn st -u' is done.
Whops, sorry, I should have read the Help more carefully.
> "non-versioned" in text but "added" in remote text can only mean that
> the files/folder is *not* under version control in the working copy
> someone else has added them and committed them to the repository.
> A simple update would/will result in an error, and the files/folder
> be marked as "obstructed" - because they're present in the working
> but not versioned, and they would have to be replaced by the versioned
> ones fetched from the repository.
I found it hard to believe in my case as that developer is the only one
in the whole company to work on that piece of code, and always have
been. So even if theoretically it is possible I don't think this is the
Anyway, we did tried and delete the files, update the WC and then check
for modifications and the messages were the same.
> We're now at version 1.4.1 with TortoiseSVN. Please update first
> asking any more support questions. We only provide support for the
> latest version here, anything else would be a waste of time (it's not
> if you'd have to pay for an upgrade, so we take the freedom to expect
> you to update/upgrade to the latest version if you expect support).
Well we won't upgrade SVN to 1.4 just yet. We need to investigate the
impact of it first, following the concerns outlined in 1.3 release
notes. Therefore we won't upgrade TSVN either yet.
I didn't "expect" support, I just asked for help. It's not like I have
flooded the mailing list with emails. And frankly I found this attitude
of "supporting only the latest version here" wrong. I understand that
people here cannot offer help for all version of TSVN, but not even for
the previous one is on the edge of rudeness, especially when you specify
"anything else would be a waste of time", and the fact I don't have to
pay is not a good reason.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jan 4 13:14:08 2007