Re: Copy svn commmits

Thanks to you all for your replies.

@Ryan, I assume that your point is that I would still perform the Merge
operation - but into a TAG as opposed to a branch.
And instead of relying on "revisions" - I would have the naming of the
tag to assist with "rolling back" changes made (in error) to the
production system.

Despite having used SVN for several years now - I have never used merge
or path etc.
I always did these process by hand.... but though it about time I
learned a more efficient - less "human" method.

Thanks again!

John Peacock wrote:
> Ryan Schmidt wrote:
>
>> Different answer: I would have said what you're describing is a tag, not
>> a branch. Make a new tag, including a version number or the date or the
>> revision or some unique identifier in the tag name (e.g.
>> /tags/production-20080306).
>>
>
> Yes, but you should account for multiple tags generated per day, so add a
> serialization number, e.g. /tags/production-2008030501.
>
> NOTE that SVN::Notify::Mirror has explicit support for switching a remote
> working copy to a new tag (that matches a regex) as a post-commit (i.e. 100%
> automated)...
>
> John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
>

-- 
Gavin Baumanis
Principal
The Spidernet Web Design
W: http://www.thespidernet.com
E: gavinb_at_thespidernet.com
P: 03 9750-6313 (+61 39750 6313)
M: 0438 545 586 (+61 438 545 586)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org