Revisions being involved while comparing branches

2010-12-20 Thread Pablo Beltran
Is there a direct way (via cmd line) to find out the revisions involved in the summary result of differencing two branches? An easy example: svn diff http://svn.apache.org/repos/asf/subversion/tags/1.6.14/subversion/libsvn_repos http://svn.apache.org/repos/asf/subversio

Re: Revisions being involved while comparing branches

2010-12-21 Thread Daniel Shahaf
'svn info' on the 1.6.15 file will tell you that. (thanks cheap copies) 'dig the logs' is "lookup the copyfrom revisions of the tags, and run log on replay.c for that revision range". What's wrong with that? Pablo Beltran wrote on Mon, Dec 20, 2010 at 19:22:20 +0100: > Is there a direct way (via

Re: Revisions being involved while comparing branches

2010-12-21 Thread Pablo Beltran
Maybe the point is efficiency. the *svn log -v* output for a revision range could be represented by a matrix with the revision numbers as rows and the changed paths as columns. So, for each revision is easy inquire the revised paths. That is simple because all the results are retrieved from one

Re: Revisions being involved while comparing branches

2010-12-21 Thread Daniel Shahaf
Pablo Beltran wrote on Tue, Dec 21, 2010 at 23:29:23 +0100: > Maybe the point is efficiency. > OK. > the *svn log -v* output for a revision range could be represented by a > matrix with the revision numbers as rows and the changed paths as columns. > > So, for each revision is easy inquire the

Re: Revisions being involved while comparing branches

2010-12-22 Thread Pablo Beltran
That would be a more efficient way to a achieve it but as you say that might not work in all cases. In my opinion a feature like that is enough important to be provided by Subversion via cmd line / API, because that is the one of the bridges between Subversion and Change Management tools (like Jir

Re: Revisions being involved while comparing branches

2010-12-22 Thread Daniel Shahaf
If you have concrete suggestions for improving or extending the core, we'll welcome them --- on the dev@ list please. Pablo Beltran wrote on Wed, Dec 22, 2010 at 14:26:13 +0100: > That would be a more efficient way to a achieve it but as you say that might > not work in all cases. > > In my opini

Re: Revisions being involved while comparing branches

2011-01-09 Thread Pablo Beltran
On Wed, Dec 22, 2010 at 1:25 AM, Daniel Shahaf wrote: > Pablo Beltran wrote on Tue, Dec 21, 2010 at 23:29:23 +0100: > > Maybe the point is efficiency. > > > > OK. > > > the *svn log -v* output for a revision range could be represented by a > > matrix with the revision numbers as rows and the chan