I don't know why there is anything to do with "URL's are saved in the .svn
dircotry". But you can try the following steps:
(1) Commit your changes into the actual version.
(2) Use 'svn merge' on the local copy (pointing to the moving label in the
repository) to bring the changes from actual version to the moving label.
(3) Commit the changes in the local copy (pointing to the moving label in
the repository). Make sure that you clearly state the FROM and TO revision
that you use in step 2 in the comment. This is to avoid double-merging for
next merging.
This is it. The only problem that I can think of is that the files in the
actual version and moving label will have different history. Don't know how
to get around this.
On 2/13/06, Katsu Tamura <katsu.tamura@heii.com> wrote:
>
> Hi,
>
> I've got a project where I'd like to have a moving label that I can apply
> to the most recent version of the code that has been validated for
> functionality. This would provide a stable baseline for people who want to
> update their local environment, and will still allow people to check code in
> while in intermediate phases of development. This moving label might be
> updated once a week and it would be dated and recorded for a software
> release.
>
> I have been trying to implement this using the Tags/Branching utility for
> TortoiseSVN. I want to create an exact copy of the source code directory
> structure in a single file branch which would represent the moving label.
> It seems that there is a conflict because the URL's are saved in the .svn
> dircotry. Basically, I would like to be able to commit the same working
> copy to 2 different places: one for the actual version in source control and
> the other for the moving label. Can this be done without creating a new
> directory and a copy of all the files every time? Is there anyone who I
> could talk to about this matter?
>
> Your quick response would be greatly appreciated.
>
> Thank you,
>
> Katsu Tamura
>
> 720-622-4176
>
>
>
Received on Tue Feb 14 02:18:01 2006