Re: [Swig-devel] Last call for CVS commits (Subversion Update)

[David B. <dav...@da...>]

>
> * Login to the SourceForge.net website.
>
> * Go to the project summary page (https://www.sf.net/projects/ 
> PROJECTNAME).
>
> * Click on the 'Admin' link.
>
> * Click on the 'Subversion' admin page link.
>
> * Click on the 'migrate' link on the 'Migration Instructions'  
> section of
> the page.
>
> * Key in the filename of the archive into the 'Source path' field,
> noting that it must comply with the filename restrictions previously
> described.
>
> I uploaded it to
> /home/groups/s/sw/swig/swigsvn.bz2
>
> * Check the 'Replace' check box in the same column, if you wish to
> replace the existing content with the new content to be added.
>
> no existing content, so can leave blank
>
> * Enter the value you want passed to the --parent-dir argument of the
> "svnadmin load
> <http://svnbook.red-bean.com/nightly/en/svn.ref.svnadmin.c.load.html>"
> command into the 'Destination' field. For most users, this would be  
> left
> blank. Note that the destionation directory must be created but empty
> for this to work.
>
> Leave the parent-dir field blank
>
> * Click on the 'Submit' button.
>
> * The migration will be finished within 24 hours. It could be finished
> in as soon as an hour or two, depending on the size of your CVS
> repository and the number of projects queued for migration in front of
> yours. Returning to the page will display whether it completed, failed
> or is still in queue.
>
>
> After the repository is updated, an admin will need to do section 9
> (just below the stuff I copied above).  The svnnotify hook should be
> enabled.
>

I have carried out these steps.   Now we wait...

Cheers,
Dave