Dave Wolfe wrote:
> I just did something hackish in an attempt to prevent people from
> accidentally committing under the wrong username on a shared dev box in
> our office. (I keep checking the logs and seeing my username next to
> commit messages that I didn't write!)
>
> So I wrote the following one-line batch script:
>
> REM TSVNAuthClobber.bat
> del /q "C:\Documents and Settings\Gforce\Application
> Data\Subversion\auth\svn.simple\*.*"
>
> and told the Task Scheduler to run it on startup, and every 60 minutes
> thereafter. (I wanted to run it when users log off, too, but there
> doesn't seem to be an option for that in Task Scheduler.)
>
> This kinda/sort works, but leaves me wondering if there's not already a
> better way? Can I make TortoiseSVN pop up an (already-populated)
> username/password confirmation dialog so that people will remember to
> log in as themselves if the cached username isn't theirs?
That's not possible with TSVN, and I think it never will. To do that,
we'd have to find a way to clear the stored auth info inside the
%APPDATA%\Subversion\auth\svn.simple\ directory which is associated with
the working copy you try to commit. And since the auth data is stored in
a file which name is the md5 hash of the auth challenge the server
sends, we can't know the exact filename without authenticating with the
repository server first.
Of course, we could just *not* use any stored auth data at all, but then
again that would mean not using it for all working copies.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Feb 13 19:53:35 2006