"C. Michael Pilato" <cmpil...@collab.net> writes: > On 04/17/2013 07:34 AM, Bert Huijben wrote: >>> With 1.6 and 1.8 I get: >>> >>> $ svn up wc/some-file-that-does-not-exist >>> At revision 3 >>> >>> With 1.7 I get: >>> >>> $ svn up wc/some-file-that-does-not-exist >>> Updating 'wc/some-file-that-does-not-exist': >>> At revision 3 >>> >>> Is it valid for these update to be successful? Should we be returning >>> an error if the update target doesn't exist in the intial working copy >>> and doesn't get added by the update? >> >> I'm not sure if we should make it an error, but a warning (=notification) >> would be friendly. > > +1. More than once I've mistakenly mis-issued an 'update' command and > wished that Subversion had told me I'd made the mistake.
I'm not planning to implement it at present so I've raised: http://subversion.tigris.org/issues/show_bug.cgi?id=4353 -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
