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

Re: M-x big-picture

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2001-02-06 00:50:37 CET

> That code is a bit out-of-date. Try writing a delta construction
> algorithm.

This was a little cryptic, but I think I understand. A client wants
to update from rev X to rev Y, and you have to generate an edit. As
part of the edit, you have to get from one version of a directory to
another, which means for each entry that changed, you have to apply a
sub-delta, and to do that you want to choose the most closely related
ancestor to make a delta from.

I've been wondering whether directories need to be handled differently
from files, such that the history of directory operations is kept
rather than just (possible optimized) storage of the contents at each
revision. This sort of encompasses Greg Stein's point that we could
lose information from a copy or rename operation because we don't keep
track of where a new entry was copied or renamed from. But that's a
very complicated proposition.

Anyway, thanks. If I come up with something concrete, I'm sure the
list will hear about it. :)
Received on Sat Oct 21 14:36:21 2006

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.