> From: allan juul [mailto:allan@muly.dk]
>
> everytime we built and deploy our Mainline branch to our production
> machines we will automatically need to update the Maintain branch to
> consist of an exact snapshot of that Mainline branch just deployed.
If you *never* make any changes to the Maintain branch other than to update
it to match the Mainline at a particular moment, then the easiest method is
to consider Maintain to be a resetable tag -- svn delete
http://.../Maintain; svn copy http://.../Mainline http://.../Maintain. That
actually does maintain the log history because Subversion records that rev
40 of Maintain is a copy of rev 38 of Mainline, which is a changed version
of rev 36 of Mainline, etc.
But if you expect to make minor changes to the Maintain branch, then you
really should set up a "vendor branch" structure as described in the
Subversion book. It looks like a lot of work, but anything simpler gets
confused by one or another normal maintenance activity.
Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 25 00:13:49 2005