Ryan Flynn wrote:
>>To build a particular version of file123.exe:
>>
>>file123.exe[1.3] = file1.c[1.1] + file2.c[1.2] + file3.c[1.3]
>>file123.exe[1.2] = file1.c[1.1] + file2.c[1.1] + file3.c[1.2]
>>file123.exe[1.1] = file1.c[1.1] + file2.c[1.1] + file3.c[1.1]
>>
>>How do I perform a code-freeze such that I can retrieve all the
>>particular versions of all the files needed to build file123.exe[1.2] ?
>>
>>
>>
>
>Asif,
>
>when a change is commited, the entire repository gets a revision
>number. so even if file3.c is the only file commited as revision, say,
>5, then you can check the entire project out at -r5 and get the other
>files as they were at the time of the file3.c commit
>
>to get a extra copy: svn checkout -r5 url/path/to/proj proj-r5
>or update your current wc to r5: svn update -r5
>
>warning: i am pretty new to svn, use this advice with caution.
>
>hope this helps.
>
>
In princip is this correct. But after 3 months of developing for example
who could remember the exact revision number :-)
If you read the svn book: there is a example for the project layout:
trunk, tags, branches! A "tag" would be a perfect idea for a freaze. In
reality a tag in svn is nothing else than a copy you make from your
trunk into a dir under tags: for example /tags/freeze_v1.0 or whatever.
-- Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 25 00:19:01 2004