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

Initial Move Support in /trunk now

From: Stefan Fuhrmann <stefan.fuhrmann_at_wandisco.com>
Date: Mon, 23 Sep 2013 00:51:15 +0200

Hi there,

As of r1525442, there is a new svn_fs_move() API supported
by all backends with BDB providing only rudimentary support.

It turned out that move() should not implicitly issue a delete()
on the source node as this creates all kinds of ordering issues
and, worse, makes it hard to verify incoming changes. Instead,
just call move() as you would call copy() today and issue an
explicit delete() for the source path.

As of r1525467, there 'svn log' now supports all moves across
all RA layers and introduces a new "--auto-moves" option that
reports many of the legacy DEL/ADD pairs as DEL/MOVE now.
Since the actual implementation of that mapping logic is in the
svn_repos layer, other functions may use this feature as well
in the future.

Currently, 'svn log --stop-on-copy" does not follow moves, yet
but instead stops at moves just like on any copy.

-- Stefan^2.
Received on 2013-09-23 00:51:52 CEST

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