{ "info": { "author": "The cvs2svn team", "author_email": "dev@cvs2svn.tigris.org", "bugtrack_url": null, "classifiers": [ "Development Status :: 5 - Production/Stable", "Environment :: Console", "Intended Audience :: Developers", "Intended Audience :: System Administrators", "License :: OSI Approved", "Natural Language :: English", "Operating System :: OS Independent", "Programming Language :: Python :: 2", "Topic :: Software Development :: Version Control", "Topic :: Software Development :: Version Control :: CVS", "Topic :: Utilities" ], "description": "cvs2svn_ is a tool for migrating a CVS repository to Subversion_, git_,\nBazaar_, or Mercurial_. The main design goals are robustness and 100% data\npreservation. cvs2svn can convert just about any CVS repository we've ever\nseen, including gcc, Mozilla, FreeBSD, KDE, GNOME...\n\n.. _cvs2svn: http://cvs2svn.tigris.org/\n.. _Subversion: http://svn.tigris.org/\n.. _git: http://git-scm.com/\n.. _Bazaar: http://bazaar-vcs.org/\n.. _Mercurial: http://mercurial.selenic.com/\n\ncvs2svn infers what happened in the history of your CVS repository and\nreplicates that history as accurately as possible in the target SCM. All\nrevisions, branches, tags, log messages, author names, and commit dates are\nconverted. cvs2svn deduces what CVS modifications were made at the same time,\nand outputs these modifications grouped together as changesets in the target\nSCM. cvs2svn also deals with many CVS quirks and is highly configurable.\nSee the comprehensive `feature list`_.\n\n.. _feature list: http://cvs2svn.tigris.org/features.html\n.. _documentation: http://cvs2svn.tigris.org/cvs2svn.html\n\nPlease read the documentation_ carefully before using cvs2svn.\n\n\nLatest development version\n--------------------------\n\nFor general use, the most recent released version of cvs2svn is usually the\nbest choice. However, if you want to use the newest cvs2svn features or if\nyou're debugging or patching cvs2svn, you might want to use the trunk version\n(which is usually quite stable). To do so, use Subversion to check out a\nworking copy from http://cvs2svn.tigris.org/svn/cvs2svn/trunk/ using a command\nlike::\n\n svn co --username=guest http://cvs2svn.tigris.org/svn/cvs2svn/trunk cvs2svn-trunk\n\n(the password is empty; i.e., just press return).", "description_content_type": null, "docs_url": null, "download_url": "http://cvs2svn.tigris.org/servlets/ProjectDocumentList?folderID=2976", "downloads": { "last_day": -1, "last_month": -1, "last_week": -1 }, "home_page": "http://cvs2svn.tigris.org/", "keywords": null, "license": "Apache-style", "maintainer": null, "maintainer_email": null, "name": "cvs2svn", "package_url": "https://pypi.org/project/cvs2svn/", "platform": "UNKNOWN", "project_url": "https://pypi.org/project/cvs2svn/", "project_urls": { "Download": "http://cvs2svn.tigris.org/servlets/ProjectDocumentList?folderID=2976", "Homepage": "http://cvs2svn.tigris.org/" }, "release_url": "https://pypi.org/project/cvs2svn/2.3.0/", "requires_dist": null, "requires_python": null, "summary": "CVS to Subversion/git/Bazaar/Mercurial repository converter", "version": "2.3.0" }, "last_serial": 1192188, "releases": { "2.2.0": [], "2.3.0": [] }, "urls": [] }