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

Re: possible improvement to svn log with "forward" revision range

From: Avalon <third-chance_at_gmx.de>
Date: Thu, 19 May 2011 22:18:42 +0200

I wanted to take a closer look into implementing this feature and have built the current SVN trunk.
I have looked through the code and now i have a rough understanding how the log information is collected.

> There are now two different issues brought up in these thread:
> 1. For 'svn log -rX:Y PATH_at_PEG, where Y> PEG, don't croak when PATH_at_Y
> doesn't exist. Instead, automatically substitute for Y the last revision in
> which PATH_at_THAT-REV *did* exist, and continue the operation. I believe this
> is something that we can reasonably achieve without too much trouble and,
> more importantly, in a client-side change (which helps with client/server
> compatibility).

As far as i know the history is always collected from youngest to oldest revision (not the other way around).
Your suggestion to modify Y to the latest revision where PATH_at_PEG still exists looks like the easiest approach.
But i could not yet figure out how to perform this operation.

Could you give me an advice how this could be realized or point me to some other code area where a similar "forward" traversal/search is performed?
May be with some hints i can carry on with this by myself.

Received on 2011-05-19 22:19:14 CEST

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.