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

Re: Defining atomic "replace"

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Wed, 12 Aug 2009 00:31:11 +0100

On Wed, 2009-08-12, Julian Foad wrote:
> > (*) Atomic move
> > In the new editor callbacks, there is a separate move() call to represent
> > atomic moves. It is thus possible to issue a delete() followed by a move()
> > to the same path that was deleted. Which is, essentially, a replace!
> >
> > --> We need to also add a REPLACES_REV argument to the move() callback, and
> > we need to disallow issuing a delete followed by a move to the same path.
> > Actually, has this case ever been considered? Currently, a move() becomes an
> > "add-with-history" plus a delete(). Our API doesn't indicate a move
> > replacing a path.
> I think the current representation of this would be two deletes (delete
> the move-source and delete the node being replaced) and then an
> add-with-history.
> > We could need another update/status letter for this.
> For now, it can recreate the existing indication(s) on multiple lines.
> D move-source-path
> D replaced-path
> A+ replaced-path (copied from move-source-path)

Or rather

D move-source-path
R+ replaced-path (copied from move-source-path)

- Julian

Received on 2009-08-12 01:31:42 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.