#1 Migrate exisiting CVS repository to a GIT repository

None
open
None
7
2012-12-30
2011-12-20
No

Migrate the existing CVS repository to a SVN repository, retaining all history.

Discussion

  • One of the reasons to migrate the code repository from CVS to SVN is to enable the migration of the project itself to the new SourceForge code. As per SF support # 23262, that can now be done with the jamlib project itself, as follows: Project Admin -> Settings, then on the right side, "Opt-in Update".

     
    • summary: Migrate CVS repository to an SVN repository --> Migrate exisiting CVS repository to a GIT repository
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -Amongst other reasons, the new SourceForge project will not be supporting CVS repositories \(at least, not anytime soon from what I understand\).    May have subprojects later that use GIT repositories but for now, migrate the existing CVS repository to an SVN repository, retaining all history.
    +Migrate the existing CVS repository to a SVN repository, retaining all history.
    
    • milestone: -->
     
  • Ticket was originally opened to migrate the existing project CVS repository to an SVN repository because at the time the ticket was opened, the migration process could not handle CVS repositories. They fixed that issue and the project has been migrated to the SF project environment. Update the ticket for migrating the CVS repository to a GIT repository, which will become the primary code repository for the JAMLIB code repository.