On 3 March 2012 09:29, Daniel Shahaf <danie...@apache.org> wrote: > Greg Stein wrote on Sat, Mar 03, 2012 at 04:20:33 -0500: >> On Sat, Mar 3, 2012 at 04:02, Daniel Shahaf <danie...@apache.org> wrote: >> >> >>> The release tarballs and signatures can be svn mv'ed from the >> >> >>> https://dist.apache.org/repos/dist/dev/httpd/ repository across to the >> >> >>> https://dist.apache.org/repos/dist/release/httpd/ repository. >> >> >>> << >> >> >>> >> >> >>> I've tried using svn mv directly on a test repo (i.e. not using a >> >> >>> workspace), and it does not seem to be possible to move multiple files >> >> >>> at once. >> >> >>> >> >> >>> Can I ask for a bit more detail on how you actually do the move? >> > >> > 1) >> > svnmucc -m logmsg -U https://dist.apache.org/repos/dist/ \ >> > mv dev/subversion/subversion-1.7.4.tar.bz2 \ >> > release/subversion/subversion-1.7.4.tar.bz2 \ >> > mv dev/subversion/subversion-1.7.4.tar.bz2.asc \ >> > release/subversion/subversion-1.7.4.tar.bz2.asc >> > >> > 2) >> > svn mv >> > https://dist.apache.org/repos/dist/dev/subversion/subversion-1.7.4.tar.bz2 >> > \ >> > >> > https://dist.apache.org/repos/dist/dev/subversion/subversion-1.7.4.tar.bz2.asc >> > \ >> > https://dist.apache.org/repos/dist/release/subversion/ >> > >> > 3) >> > svn mv https://dist.apache.org/repos/dist/dev/subversion/1.7.4/ \ >> > https://dist.apache.org/repos/dist/release/subversion/ >> > >> > 4) >> > svn mv https://dist.apache.org/repos/dist/dev/subversion/1.7.4/ \ >> > https://dist.apache.org/repos/dist/release/subversion/1.7.4/ >> > >> > Does that answer your question? >> >> I work on the same project as you, Daniel, and even for me, that was >> certainly.... opaque. >> >> Looks like you are providing four different alternatives to move from >> "development review" to "release". Did I get that right? >> > > Yes, I was providing four different ways to move the tarballs+signatures > from the dev/ tree to the release/ tree. > >> A bit of exposition would be nice. >> > > Next time, sure.
So how was the following commit acheived? svn log -r397 -v https://dist.apache.org/repos/dist/ 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) And when might one use the different options? For example, how does 4) differ from 3)? Won't 4) end up creating subversion/1.7.4/1.7.4/ ? Also 1 & 2 seem to relate to different directory layouts compared with 3 & 4. As far as I can tell, 3&4 assume each release has a different subdirectory, which is not the case with httpd at present. Using a separate sub-directory per release makes it trivial, but is not going to suit all projects.
