[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Update targets that don't exist

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 17 Apr 2013 11:54:07 +0100

We allow the user to update a target that is not present in the working
copy: it lets the user bring in a target that is present in a different
revision. We also allow the update of an existing target to a revision
in which the target does not exist: the target gets marked as
'not-present'. Both of those behaviours are useful but what about a
target that does not exist in the working copy and does not exist in the
target revision? The update doesn't change the working copy but it
doesn't give an indication that the target doesn't exist either.

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?

Certified & Supported Apache Subversion Downloads:
Received on 2013-04-17 12:55:02 CEST

This is an archived mail posted to the Subversion Dev mailing list.