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

Re: damned 'svn log' behavior

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-02-22 19:00:13 CET

Greg Stein <gstein@lyra.org> writes:

> So I'm sitting at the trunk, yet the -r 5000 doesn't show me that a change
> was made underneath my current position.

It absolutely does! In revision 5000, there were no changes within
/trunk. Mike's commit was within /branches.

> 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.

Absolutely not. If I run 'svn log -rX:Y', I only want to see
changes that happened within '.', not changes for the entire damn
repository!

> 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.

I have to wonder, why are you constantly asking for the log of a
single specific revision?

> Ick icky. We're talking about user workarounds here, and changing
> patterns of behavior from obvious to non-obvious.

As a compromise, perhaps we can add a switch to 'svn log' which forces
it to run against the root of repository.

(FWIW, I've never been bitten by this problem. I run 'svn log' on
specific files, or on ranges of revisions. But I never find myself
asking for a specific revision out of thin air. I wonder why your
use-cases are so different?)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 22 17:02:45 2003

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