[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Updating the repository from wildcat user update

From: Ron Wilson <ronw.mrmx_at_gmail.com>
Date: Tue, 29 May 2012 14:43:37 -0400

On Tue, May 29, 2012 at 7:21 AM, Steve Swift <steve.j.swift_at_gmail.com> wrote:
>
> 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
>
> Is there a more elegant way to have handled this?
>
> At the very least, it would have been nice had the update appeared to have
> come from my colleague's ID and not mine.

Is there a reason this (or other people like him) to not use SVN?

It is possible to use the Precommit hook to insure that such emergency
fixes only go to a particular branch so such fixes do not interfer
with the normal development and release processes. Then the original
commit of the fix would be from whomever did the fix, and whomever
merged the fix into the next production release would be the commiter
of the merge.

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

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

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.