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

Re: svn bug

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2005-11-24 21:32:37 CET

On Thu, Nov 24, 2005 at 01:33:16PM -0500, Greg Hudson wrote:
> Uh, that seems inconsistent with the rest of the command set.
> I can "svn cat http://svn.collab.net/repos/svn/trunk/COMMITTERS@2753" to
> get a very old version of the COMMITTERS file. But if I do the same
> command with "svn blame", I get a blame of the current version.

I always figured that 'path@rev' just allowed the user to locate a
particular line-of-history, and that the -rREV option then chose the
revision to perform the operation on. Given that the default revision
for 'cat' is HEAD, I'm surprised that it behaves this way - it seems to
conflate the two concepts.

We should be consistent though. Apart from 'cat', which of the commands
that accept a peg-revision default to -rPEGREV if no revision argument
is provided (and which don't)?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 24 21:33:21 2005

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