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

Re: [RFC] Move tracking - design summary and mock-up proposal

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 20 May 2014 17:21:30 +0200

On Tue, May 20, 2014 at 03:25:39PM +0100, Julian Foad wrote:
> Hi, folks.
> At last I have a plan for move tracking. I want to share this plan and get
> your feedback.

I'm delighted to hear this! :)

> I want to start implementing it, but first Philip suggested, and I agree,
> we should do a mock-up and see how the high-level behaviour pans out in
> typical scenarios involving moves, especially merging with moves. There's a
> lot of work here and implementing it would be risky unless we first check
> whether it will deliver useful results.
> I'd prefer to do the mock-up in Python if we can. Does that seem
> reasonable, or should I branch and hack the C code instead?

I would branch and hack the C code. Most of the actual behaviour
changes will have to be in libsvn_client/libsvn_wc. The client
only controls prompting and can only offer meaningful choices
if the library provides enough information and does right thing
when asked to do something. I expect we'll have to make changes
in the conflict resolver, and perhaps the conflict store as well.

Also, we're already familiar with the C code and can collaborate
on the branch.

> == DESIGN ==

I'll review the design later.
Received on 2014-05-20 17:22:09 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.