Re: Updating the repository from wildcat user update

On Tue, May 29, 2012 at 7:21 AM, Steve Swift <steve.j.swift_at_gmail.com> wrote:
> We're just at the point of migrating to SVN, but we had a problem at the weekend which required the duty person to apply an emergency fix. He had his own copy (not a working copy) of the code, so he updated three files, compiled it, and fixed the problem.
>
> This left me with the issue of integrating his updates back into the repository.
>
> I compared his files with my working copy, and there were only three files that differed. So far, so good. I copied his files into my working copy, and committed the update. Back on a level keel.
>
> Is there a more elegant way to have handled this?

Absolutely. You have the "duty person" operate out of his own WC to
create the emergency fix, commit it and apply it. Your build/release
process should always be the same - when you allow exceptions like
this, bad things start to happen. In emergency situations, you just
get the process expedited.

> At the very least, it would have been nice had the update appeared to have come from my colleague's ID and not mine.

So why didn't he/couldn't he commit it himself?

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2968212

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-06-02 03:10:07 CEST