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

Re: Providing accurate progress information during operations

From: Joshua Varner <jlvarner_at_gmail.com>
Date: 2005-07-16 17:29:28 CEST

On 15 Jul 2005 03:12:42 -0500, C. Michael Pilato <cmpilato@collab.net> wrote:
> SteveKing <steveking@gmx.ch> writes:
> > AFAIK Subversion stores the delta in a tempfile before committing, so
> > the size should be known.
> I believe this to be untrue. IIRC, the new fulltext is squirreled
> away in a tempfile so that a) a user who has left a to-be-committed
> file open in his editor doesn't accidentally change the file while
> deltas are being calculated later, and b) so it can be installed as
> the new pristine copy. Deltas are generated streamily and never land
> on the disk.
Would it be possible for an IDE based client (that normally controls
all access to the files) to provide the diffs to svn. For example,
subclipse (which I don't use, so I may be completly off-base) could
generate the diffs every time it sees a file saved by Eclipse and keep
track of the list of changed files, so rather than crawl the working
copy it just checks its cache and then feeds the diffs directly to the

This would bypass the upfront work by spreading it out and allow the
progress reporting. Given this would increase the complexity of
subclipse, but would it be possible if they wanted to try it? If it
was possible to cache the diffs, I would probably add a hook into
emacs to generate those on save if the cost is low.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 16 17:30:07 2005

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.