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

Re: SVN compatibility question

From: Branko ─îibej <brane_at_apache.org>
Date: Fri, 1 Apr 2016 11:00:14 +0200

On 01.04.2016 10:21, Johan Corveleyn wrote:
> On Fri, Apr 1, 2016 at 9:32 AM, Stefan Sperling <stsp_at_elego.de> wrote:
>> On Fri, Apr 01, 2016 at 05:36:34AM +0000, Daniel Shahaf wrote:
>>> Normally, 'svn mv' does two things: (a) rename the file on disk,
>>> (b) record in .svn/ that the rename had happened. As of 1.8, we allow
>>> the user to tell 'svn mv' to do only (b). We don't expose that ability
>>> in the standard command-line client, but it's available to API users
>>> (such as tortoisesvn and bindings scripts) via the 'metadata_only'
>>> parameter to svn_client_move7().
>> I've been thinking that allowing users to perform a metadata-only move
>> with 'svn mv' might save people running into this common rookie mistake
>> some hair... If they look at 'svn help mv' to find this new hypothetical
>> --meta-data-only option, that is. (We could re-use the --record-only
>> option from 'svn merge' as a name.)
> +1. Sounds like a good idea to me.

Yup, and ditto for 'svn copy'; I know that SmartSVN has an option to
find and fix up such mistakes, and apparently that's a very popular feature.

-- Brane
Received on 2016-04-01 11:00:19 CEST

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

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