On Wed, Jun 25, 2008 at 7:13 PM, Wade Tregaskis <wtregaskis_at_apple.com> wrote:
>>> Subject pretty much says it all. There's no reason for it to do so; it
>>> manages with any other command I use just fine.
>>
>> Could you give a little bit more information? Are you running multiple
>> invocations of 'svn blame', or just one? What authentication method are you
>> using? Which version of Subversion?
>
> svn+ssh. It occurs with version 1.4 or 1.5. All I'm doing is running "svn
> blame file1.c file2.c etc". For every other command I'm familiar with, I'm
> prompted only once per run of 'svn' for my password, which makes sense and
> is what I want.
>
> In many cases I'm on a temporary machine and setting up ssh keys is more
> pain than it's worth. It's also convenient from a security perspective as I
> don't have to worry about caching; my password is required for every single
> 'svn' invocation. I'm sure I can fiddle with ssh-agent and whatnot to have
> immediate timeouts, but, why bother (and, would it even solve the issue at
> hand in such a case?) ?
Yes, it would solve the issue at hand. The Subversion code has been
written on the assumption that connections are light-weight objects
which can be created whenever necessary. Blame creates a connection
per target and disposes of that connection right after completion.
Noticing it needs another file blamed, it sets up a new one.
Bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-25 23:59:06 CEST