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

Re: Crash in nightly build r14078

From: Robert Dailey <rcdailey_at_gmail.com>
Date: Tue, 30 Sep 2008 14:25:20 -0500

On Tue, Sep 30, 2008 at 2:12 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> Robert Dailey wrote:
>> On Tue, Sep 30, 2008 at 1:49 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>>> Robert Dailey wrote:
>>>> On Tue, Sep 30, 2008 at 12:44 PM, Stefan Küng <tortoisesvn_at_gmail.com
>>>> <mailto:tortoisesvn_at_gmail.com>> wrote:
>>>> So you were able to view the repository without specifying a password?
>>> No, not that. But I could debug why TSVN from trunk didn't ask for a
>>> username/password but showed the error immediately.
>> Ah, I see!
>> Could you explain what the problem was if it isn't too inconvenient?
>> I'm curious to know :)
> I've implemented a custom auth handler which caches username/password
> during a TSVN session (that helps if the auth is not saved: for example
> the repo browser will only ask for it once, then this custom auth
> handler returns the cached credentials).
> But that handler always returned credentials, even if no creds were
> cached before: in such cases it returned empty usernames/passwords
> instead of nothing.
>> Glad I could help! You know, I'm reporting so many bugs that at this
>> point posting to the dev mailing list may be the less efficient method
>> of reporting issues. Do you have a preferred location for bug reports
>> (and feature requests), Stefan? Or is the dev mailing list perfectly
>> fine?
> The dev mailing list is the right place. That's what I read every day.

Thanks for the clear technical description of the problem. Keep up the
great work, as usual!

To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-09-30 21:25:34 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.