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

Re: Consistency between 'update' and 'switch' APIs

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Sat, 6 Apr 2013 20:55:01 +0100 (BST)

Julian Foad wrote:

> C. Michael Pilato wrote:
>> [...]  So I agree, both switch and update should carry the
>> server-recognized meaning of 'ignore-ancestry' in both the client
>> and RA layers.

In r1465292 I added the 'ignore_ancestry' flag to the RA 'update' APIs, for consistency with 'switch'.

That's enough to satisfy my symmetry cravings at the moment.  I do not currently intend to add that flag to the svn_client 'update' API and the 'svn up' UI.  I don't think there is a good reason to add it to the APIs that implement 'svn status --show-updates'.  Nor do I intend to do anything about the other inconsistencies (the 'adds_as_modifications' and 'ignore_unver_obstructions' flags that are available for 'update' but not 'switch') in the short term, although after 1.8 I might.

- Julian
Received on 2013-04-06 21:55:36 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.