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

RE: Re: Missing “transferred kbytes” in TortoiseSVN update or checkout dialog

From: Markus Liebelt <markusliebelt_at_gmail.com>
Date: Mon, 29 Jun 2015 05:31:24 -0700 (PDT)

Thank's a lot for the answer, even when there is some feedback included I don't like :-)

> On 17.06.2015 21:36, Markus Liebelt wrote:
> > See my question at Stackoverflow about that topic. There was no interest at all to that question and an answer.
> >
> > http://stackoverflow.com/questions/30845540/missing-transferred-kbytes-in-tortoisesvn-update-or-checkout-dialog
> >
> > I would like to know the following things:
> >
> > * What is the reason that this feature was removed?
> > * Is there a way to bring it back to the client?
> First, this is a user question and belongs to the users list.

I have a different opinion here. If there would be a flag, users could answer that. But the reason for removing the feature could only be explained by developers.

> Second: if you post a question to stackoverflow and then ask it here
> again, at least quote the question here and not just a link.

Ok, here is the summary of the question, so others have not to click on the link:

In former times, with older versions of TortoiseSVN (I think at least TortoiseSVN 1.6.x), I got the feedback how many kbytes or mbytes were transferred when using the checkout or update dialog in TortoiseSVN.

Nowadays (with TortoiseSVN 1.8.x), this information is just missing. When I do a checkout, I see during the checkout the information flying through Transferring at x kbytes/sec, but at the end, I only get: Added: x

Why is that information not any more visible? Is there a way to see it again?

> As for why it was removed: I got tired of explaining why the total
> amount of transferred data didn't match with what users expected. And
> since it rarely matched the expectations, why even show it?
> Reasons for why it doesn't match:
> the total bytes transferred include authentication data (can be a *lot*
> when authenticating against a domain), the data can be compressed, only
> changes are sent/received and not whole files, ...

I do understand that, for us this feature was handy to see the following things:

* How much do we have to expect on network traffic in special situations? Sometimes, we could even measure the quality of the network (including authentication / authorization) of different users.
* The number (at least when doing a checkout) gave us feedback how big that checkout was.

So thank's a lot for the information, and sorry for using the wrong forum and form of asking.


To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-06-29 17:20:12 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.