Re: Question on release process - making release public by svn move

sebb <sebbaz_at_gmail.com> writes:

>>> Whatever was used to generate that commit is good because it shows
>>> clearly that the release files were derived from the dev files, for
>>> example:
>>>
>>>   R /release/httpd/CHANGES_2.2 (from /dev/httpd/CHANGES_2.2:396)
>>>   A /release/httpd/CHANGES_2.2.21 (from /dev/httpd/CHANGES_2.2.21:396)
>>
>> I don't know what httpd folks did there.
>
> Neither do I, which is where this all started ...

You can do it with svnmucc:

$ svnmucc -U http://localhost:8888/obj/repo \
     rm release/httpd/f \
     cp head dev/httpd/f release/httpd/f \
     cp head dev/httpd/g release/httpd/g

$ svn log -vqr4 http://localhost:8888/obj/repo
------------------------------------------------------------------------
r4 | (no author) | 2012-03-09 19:51:58 +0000 (Fri, 09 Mar 2012)
Changed paths:
   R /release/httpd/f (from /dev/httpd/f:3)
   A /release/httpd/g (from /dev/httpd/g:3)
------------------------------------------------------------------------

Or you could use the Subversion bindings to drive the RA layer.

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com