[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: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-07-17 02:48:11 CEST

Joshua Varner <jlvarner@gmail.com> wrote on 07/16/2005 11:29:28 AM:

> 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
> server.

Subclipse (and TortoiseSVN) know and provide the list of files to commit,
but we do not provide the diffs. As far as Subclipse is concerned, that
is not something I would want to see us try to do. Commit is not really
the problem anyway, it is really checkout and update. When you do a
commit, you have a pretty good idea of what you are sending the server and
how long it will take, and the commit operation itself sends reasonably
decent status info to let you know what is doing. It would be nice if it
output some kind of bytes transferred info, but it is not critical.

I think checkout, and especially update, are the areas this is most
needed. Even if it was just the server saying "I am going to send you 16
files" before it sent any, that would be an improvement. Switch and merge
could also benefit from this.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 17 02:48:51 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.