kfogel@collab.net wrote:
> "Andy Peters" <devel@latke.net> writes:
>
>> we like to include the resulting
>>PROM load files with the sources that we hand over to production. It
>>would be convenient to check these results files into the repository.
>>It seems to me the right way to do this would be to use a tag.
>> Would it be
>>better to simply add the build results to the WC, commit the change,
>>tag it (leaving the WC still referring to the trunk), then svn delete
>>the build results? All thoughts appreciated. -- a
>
> Why not just do this instead?
>
> $ cd your_regular_trunk_working_copy
> $ cp ../../../wherever/prom_load_file .
> $ svn add prom_load_file
> $ svn cp -m "Create Release 2.3 tag." . http://.../repos/tags/release-2.3
> $ svn revert prom_load_flie
> $ rm prom_load_file
> $ svn ls http://.../repos/tags/release-2.3/
> ...
> ...
> prom_load_file
> ...
> ...
> $
Ahhhh, yes, I like that!
Thanks!
-a
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 30 05:06:02 2005