subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nico Kadel-Garcia <nka...@gmail.com>
Subject Re: Default user on commit
Date Mon, 21 Apr 2014 19:33:09 GMT
On Mon, Apr 21, 2014 at 8:17 AM, Zé <jose.passes@gmx.com> wrote:
> On 04/19/2014 02:22 AM, Nico Kadel-Garcia wrote:
>>
>> On Fri, Apr 18, 2014 at 1:53 PM, Branko Čibej <brane@wandisco.com> wrote:
>>>
>>> On 18.04.2014 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"?
>>
>>
>> sudo to another username when working with the other repository?
>>
>
> It doesn't make much sense to create a new username just to handle a remote
> repository.  In fact, that's not even possible if the user hasn't admin
> privileges.

He's not just "handling a remote repository". He's submitting commits
as that other user. Keeping the behavior as yourself versus the
behavior as another user, separated in userland, is precisely the sort
of task that "sudo" was designed for. It may not be the *best* way in
this case, but it's workable in many environments.

Mime
View raw message