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

Re: Plumbing work to make shelving complete and robust

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Fri, 24 Aug 2018 14:25:52 -0400

On Fri, Aug 24, 2018 at 12:26 PM Julian Foad <julianfoad_at_apache.org> wrote:

> Only by implementing more than one edit driver for each editor (and vice
> versa) can we prove that the components are cleanly separated by an API and
> thus re-usable.
> Then there is the need for a test framework that can generate all
> different combinations of changes and test each of the subsystems with all
> of those changes.
> These improvements are not just to benefit shelving. In the longer term,
> if we are to make a major improvement like supporting moves/renames
> properly, in my opinion we need to do it starting from a baseline where we
> consistently and cleanly use APIs that encode the current semantics of
> versioned changes, and then migrate those.
I'm not expert enough on Subversion internals to give in-depth
technical feedback here, but overall this refactoring sounds like a
good game plan, as it will improve consistency and testability, and
it sounds like it will make it possible (and/or easier) to
implement all sorts of nifty new features in the long run. Not only
should this benefit shelving, but checkpointing (which in my view
seems like an extended version of shelving) should benefit
significantly as well.
Received on 2018-08-24 20:26:14 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.