'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 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/subversion/tags/1.6.15/subversion/libsvn_repos--summarize > > M > http://svn.apache.org/repos/asf/subversion/tags/1.6.14/subversion/libsvn_repos/replay.c > > ======================== > > The two tags were created in r1036188 and r1038150, but the replay.c file > was modified in > http://svn.apache.org/repos/asf/subversion/branches/1.6.x/subversion/libsvn_repos/repla...@1037005 > > Is there anyway to find out the 1037005 revision number without having to > analyze the logs?