Nathan Hartman to Anton Shepelev: > > That was my initial suggestion, too, but when I tried `svn up' > > at a random location that was not an SVN working directory it > > printed: > > > > Skipped '.' > > Summary of conflicts: > > Skipped paths: 1 > > > > which is not very polite. I expected: > > > > svn: E155007: 'C:\Program Files\Far Manager' is not a working > > copy > > Interesting. I think you are using an older Subversion client. For > example, Subversion 1.8.14 prints this when I run "svn update" in > a random non-working-copy directory: > > E:\junk>svn up > Skipped '.' > Summary of conflicts: > Skipped paths: 1 > > But Subversion 1.13.0 prints this: > > junk $ svn up > Skipped '.' > svn: E155007: None of the targets are working copies
Thank you. I should not have believed the handling of so basic an error has changed so recently. It it time I upgraded my svn client. -- () ascii ribbon campaign - against html e-mail /\ http://preview.tinyurl.com/qcy6mjc [archived]
