From: Michael Haggerty <mhagger@alum.mit.edu>
To: announce@cvs2svn.tigris.org,
Git Mailing List <git@vger.kernel.org>,
mercurial@selenic.com, Bazaar <bazaar@lists.canonical.com>
Subject: cvs2svn/cvs2git version 2.2.0 has been released
Date: Sun, 23 Nov 2008 10:00:18 +0100 [thread overview]
Message-ID: <49291BA2.2050604@alum.mit.edu> (raw)
cvs2svn/cvs2git 2.2.0 has been released.
cvs2svn/cvs2git [1] is a free program that converts CVS repositories to
Subversion, git, Mercurial, or Bazaar, including all project history and
metadata. cvs2svn can convert just about any CVS repository we've ever
seen, including gcc, Mozilla, FreeBSD, KDE, and GNOME. Conversion to
the DVCSs is via dumping output in git-fast-import format.
cvs2svn infers what happened in the history of your CVS repository and
replicates that history as accurately as possible in the target SCM.
All revisions, branches, tags, log messages, author names, and commit
dates are converted. cvs2svn deduces what CVS modifications were made
at the same time, and outputs these modifications grouped together as
changesets in the target SCM. cvs2svn also deals with many CVS quirks
and is highly configurable. See the comprehensive feature list [2].
Significant changes in release 2.2.0:
* By default, omit trivial CVS import branches from conversion.
* Allow vendor branches to be excluded (grafting child symbols to
trunk).
* By default, don't include .cvsignore files in output (except as
svn:ignore).
* Allow arbitrary SVN directories to be created when a project is
created.
* cvs2git:
- Omit the tag fixup branch if a tag can be copied from an existing
revision.
- Generate lightweight rather than annotated tags.
* Converting to Mercurial:
- Add an option to set the maximum number of merge sources per commit.
(Mercurial only allows a commit to have 0, 1, or 2 ancestors.)
- Allow file contents to be written inline in git-fast-import streams
(hg fast-import doesn't support predefined blobs).
* Allow the user to specify templates for cvs2svn-generated log
messages.
* Fixed a few minor bugs.
For more information, see the latest CHANGES file [3].
You can download the new release here [4]. (Its MD5 checksum is
466b757fdef5378a46bba4ceefd047a4.)
Please send any bug reports and comments to users@cvs2svn.tigris.org.
Michael Haggerty, on behalf of the cvs2svn development team.
[1] http://cvs2svn.tigris.org
[2] http://cvs2svn.tigris.org/features.html
[3]
http://cvs2svn.tigris.org/source/browse/cvs2svn/tags/2.2.0/CHANGES?view=markup
[4]
http://cvs2svn.tigris.org/files/documents/1462/44372/cvs2svn-2.2.0.tar.gz
reply other threads:[~2008-11-23 9:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49291BA2.2050604@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=announce@cvs2svn.tigris.org \
--cc=bazaar@lists.canonical.com \
--cc=git@vger.kernel.org \
--cc=mercurial@selenic.com \
--cc=users@cvs2svn.tigris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).