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

Re: svn_client_log2 doesn't take a peg revision

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-04-26 19:00:27 CEST

Greg Hudson <ghudson@MIT.EDU> writes:

> On Sun, 2005-04-24 at 03:48, SteveKing wrote:
> > While playing around with the new svn_client_log2() API and its 'limit'
> > param I noticed that this API doesn't take a peg revision. I think it
> > should.
> +1, although I won't be developing a patch for it myself.

+1, same disclaimer. :-)

> (I think some developers have considered peg-rev processing for "svn
> log" unnecessary since svn log naturally already has history-following
> logic. But that logic only applies to displaying history once we've
> found a starting point; peg-rev processing should still apply to finding
> the starting point.)

Or, it could have just been an oversight. Regardless, yeah,
history-following or not, all subcommands which operate on paths
should be peg-aware.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 26 19:05:33 2005

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