#4 Migrate CVS repository to an GIT repository

None
closed
None
5
2014-04-24
2011-12-20
No

Migrate the existing CVS repository to a new GIT repository.

Discussion

  • Robert James Clay

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

    Diff:

    --- old
    +++ new
    @@ -1 +1,2 @@
    -Amongst other reasons, the new SourceForge project will not be supporting CVS repositories \(at least, not anytime soon from what I understand\).    May have sub projects later that use GIT repositories and/or other types of code repositories but for now, migrate the existing CVS repository to an SVN repository, retaining all history.
    +Migrate the existing CVS repository to a new GIT repository.
    + 
    
    • status: open --> accepted
    • assigned_to: Robert James Clay
    • milestone: -->
     
  • Robert James Clay

    The original reason for doing a CVS to SVN migration was because the old beta SF project code did not support migration of the CVS repository. The new SF project code supports migration of CVS repositories so do not need to migrate the existing CVS repository to an SVN repository for that reason. The project has been migrated to the new code.

     
  • Robert James Clay

    Did create and make public a GIT repository (label="Git", path = "git") but I am not satisfied with how the import from CVS and the import of the most recent archives show up in it. Redoing the repository.

     
  • Robert James Clay

    Backed up the old cvs code repository using rsync. No problem testing that locally, so removed the old online CVS repository, removed the old online GIT repo then added the new GIT repo using the 'code' path, and then pushed my existing local copy of the GIT repository to the new online location.

     
  • Robert James Clay

    • status: accepted --> closed
    • Group: --> None
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks