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

damned 'svn log' behavior

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-02-22 06:10:09 CET

The behavior of 'svn log -r NNN' is really getting annoying. I don't see an
issue about this, so is it just me, or is the issue under another name?

Specifically:

$ svn info
...
Url: http://svn.collab.net/repos/svn/trunk
...
$ svn log -r 5000
------------------------------------------------------------------------
$ svn log -r 5000 http://svn.collab.net/repos/svn/
------------------------------------------------------------------------
rev 5000: cmpilato | 2003-02-20 15:20:29 -0800 (Thu, 20 Feb 2003) | 3 lines

* subversion/libsvn_fs/bdb/changes-table.c
  Fix some fn-space-paren stuffs.

------------------------------------------------------------------------
  

So I'm sitting at the trunk, yet the -r 5000 doesn't show me that a change
was made underneath my current position. I do recall at one point, that the
log was only supposed to show changes to that particular area or below. But
it doesn't even do that now.

Even so, it still seems assinine that when I ask for the log about a
specific revision, that I don't get that data. What if the change was over
in /clients/? Better to know that, then to report nothing.

What ends up happening is that 'svn log -r NNN' tends to fail for me more
often than not, and I have to use the URL form. Ick icky. We're talking
about user workarounds here, and changing patterns of behavior from obvious
to non-obvious.

Is there a rationale for the current behavior that I'm missing?

Thanks,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 22 06:05:50 2003

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.