[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: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-11-25 01:30:15 CET

On Thu, 2005-11-24 at 20:32 +0000, Malcolm Rowe wrote:
> 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.

The "svn cat" rules for URLs:
  * The default for the peg rev is HEAD.
  * The default for the operative rev is the peg rev.

Perhaps this is conflation, but it's a whole lot more convenient and
intuitive to be able to say "svn cat foo@10" than to say "svn cat -r 10
foo@10".

> 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)?

Operative rev defaults to peg rev:
  cat
  export
  info
  ls
  propget
  proplist

Operative rev defaults to HEAD:
  blame
  co (bug: @pegrev not trimmed off default wc pathname)
  diff (second operative rev defaults to HEAD)

Does not appear to support peg revs even though it could:
  cp
  log
  switch

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 25 01:31:32 2005

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