[jira] Commented: (INFRA-1672) Import missing branches from CVS into SVN

["Torsten Curdt (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757757#action_12757757 ] 

Torsten Curdt commented on INFRA-1672:
--------------------------------------

The following procedure worked for me: 

on people.apache.org: 
[code] 
    cd /home/cvs 
    tar czvf /home/tcurdt/cocoon-1.tgz cocoon-1 
[code] 

on my machine: 
[code] 
    scp people.apache.org:cocoon-1.tgz . 
    tar xzvf cocoon-1.tgz 
    mv cocoon-1 CVSROOT 
    mkdir cocoon-1 
    mv CVSROOT cocoon-1 
    svnadmin create --fs-type fsfs cocoon-1-svn 
    cvs2svn --fallback-encoding UTF-8 --retain-conflicting-attic-files --existing-svnrepos -v -s cocoon-1-svn cocoon-1 
[code]

> Import missing branches from CVS into SVN
> -----------------------------------------
>
>                 Key: INFRA-1672
>                 URL: https://issues.apache.org/jira/browse/INFRA-1672
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: CVS, Subversion
>            Reporter: Torsten Curdt
>            Priority: Minor
>
> Cocoon would like to preserve history in subversion. Some old branches were not converted from CVS. Could anyone please help with this?
> Seems like we had the following branches at people.apache.org:/home/cvs/cocoon-1
>       cocoon-1_8_2:1.11
>       cocoon-1_8_1:1.10
>       cocoon-1_8:1.8
>       cocoon-1_7_4:1.7
>       cocoon-1_7_3:1.7
>       cocoon-1_7_2:1.7
>       cocoon-1_7_1:1.7
>       cocoon-1_7:1.7
>       cocoon-1_6_1:1.5
>       cocoon-1_6:1.5
>       xml-cocoon2:1.4.0.2
>       cocoon_16_dev:1.1.1.2
>       stefano:1.1.1
>       dirkx:1.1.1.1
>       initial:1.1.1;
> It would probably be the easiest to just import them into
> http://svn.apache.org/repos/asf/cocoon/branches/
> And we do the cleanup in there.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.