After some extensive testing, it turns out --no-auth-cache is the right way to do it. As long as I use that option when using the alternate usernames, everything works like I expect it to. It’s easier than needing to remember to do at least one operation with the default username after an alternate-usernae commit. :)
On Apr 18, 2014, at 3:06 PM, Bert Huijben <b...@qqmail.nl> wrote: >> I have two local working copies, both on my local user account. I am >> managing commits for another user, so he sends me files and I check them >> in. It's weird but we have our reasons for this. >> >> So I go into his working copy, replace the file in question with his copy, >> then >> do `svn ci --username other` and it works fine. But next time I go into my >> working copy, if I commit using `svn ci` without specifying username, it >> "remembers" the alternate username. >> >> Is there a way to keep these from "sticking"? Or a way to specify a default >> username? Otherwise I'll probably just specify each time, but it's not ideal >> as >> it's too easy to forget to specify it. I had hoped that omitting the >> --username >> argument would always default to the user's local user account name, but >> that's not the case. > > You can pass --no-auth-cache with --username to avoid storing the new > credentials. > > Bert
