On Monday, February 24, 2003, at 06:32 AM, Greg Stein wrote:
> On Sat, Feb 22, 2003 at 10:00:13AM -0800, Ben Collins-Sussman wrote:
>> 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.
>
> Ah. I didn't realize it was in the branch (I just read the logmsg).
>
>>> 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!
>
> Not necessarily. I might also want to see those log messages, period.
> Consider the RM function and wanting to see all log messages since the
> last
> release.
>
>>> 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?
>
> Ever see this phrase? "Fixed in rev 5020" ? Hell yah, I often want to
> see
> log messages of single revisions. IOW, I see it as a valid use case...
>
>>> 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.
uh, i really don't see the point in yet another switch. just type 'svn
log -r FOO http://url/of/repos'. it's going to take just as long to
type as a long flag would, and i'm sure you're not proposing we waste a
short flag on something like this, right?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 24 12:44:27 2003