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

RE: Adding merge arrows on Revision Graphs

From: Kerry, Richard <richard.kerry_at_atos.net>
Date: Mon, 3 Apr 2017 13:19:23 +0000

In the Great Forking of the original CVS, which resulted in CVSNT and Subversion, CVSNT implemented the join information that this requirement needs, but Subversion did not. In the long run Subversion won the war but unfortunately the Subversion server side doesn't easily provide the information needed for this feature. I too have asked about it and got the answer as below.
My suggestion is that for this to be implemented without the speed issue as described, something needs to be added to the Subversion server to allow it to provide the required information in a tolerable timescale. It may be that the necessary information is already there in some form and could be calculated by the server to be requested by Tortoise (or any other tool). It may be that the mergeinfo already holds what is required. In the longer term it may be that if the current format of mergeinfo doesn't hold this information in a manner that may be used in a timely manner, then there could be some change made to the format, or more data stored separately. In that latter case it may be that the information required is already there but not in an easily useable form, but that a database upgrade process could recalculate it and store whatever is most useful to avoid slow on-the-fly calculations.

Just a thought,

Richard Kerry
BNCS Engineer, SI SOL Telco & Media Vertical Practice

T: +44 (0)20 3618 2669
M: +44 (0)7812 325518
Lync: +44 (0) 20 3618 0778
Room G300, Stadium House, Wood Lane, London, W12 7TA

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
Sent: Sunday, April 02, 2017 8:42 PM
To: users_at_tortoisesvn.tigris.org
Subject: Re: Adding merge arrows on Revision Graphs

On 01.04.2017 20:57, Wai wrote:
> I like to make a request to add merge arrows between branches and
> trunk. The revision graph is conceptual very incomplete without that.
> In many projects, work done in the branch is often merged back to the
> trunk. Not been able to show that in revision graph severally
> debilitates the tool.
> It looks like this request has been made in the past multiple times
> but has been pushed back or ignored perhaps due to its hidden
> complexity.

It's not really the complexity. The problem is the network and the speed.

To get that information, multiple requests to the repository have to be made. In fact multiple requests per revision.
If we assume a very fast connection to the repository, it would take about half a second to get all the information for one revision.
Now, even if your repository only has a thousand commits done (and that's a very conservative view - most projects are in the range of ten or hundred times that), that sums up to 500 seconds to get the information to show those merge info in the revision graph.

I doubt that any user would want to wait that long. And if you now say that you would, I'm sorry I won't believe you.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.
This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-04-03 15:20:06 CEST

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