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

RE: Update targets that don't exist

From: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 17 Apr 2013 13:34:07 +0200

> -----Original Message-----
> From: MARTIN PHILIP [mailto:codematters_at_ntlworld.com] On Behalf Of
> Philip Martin
> Sent: woensdag 17 april 2013 12:54
> To: dev_at_subversion.apache.org
> Subject: Update targets that don't exist
> 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?

I'm not sure if we should make it an error, but a warning (=notification)
would be friendly.
(The 'Updating' line is new in 1.7 for all updates)

Received on 2013-04-17 13:35:13 CEST

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