On 2014-04-18 18:15, Justin Mrkva 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. > > And yes, I know I could create a second local user account to make sure they > stay separate. I’d rather not, though, if there’s another way to do it. >
Since you are using dedicated working copies and also already the command line why aren't you writing a small wrapper script and place this into the root of the working copy?
