cvs2svn/cvs2git 2.4.0 has been released
Michael Haggerty <[email protected]> Sat, 22 Sep 2012 20:04:29 +0200
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <505DFDAD.60607__41711.5009543069$1348337090$gmane$org@alum.mit.edu> |
I've just released version 2.4.0 of cvs2svn/cvs2git. This release includes lots of improvements that were implemented quite a while ago but never officially released. Some highlights: * cvs2git conversions are cleaned up in a number of smallish ways. * Much faster cvs2git conversions via new option --use-external-blob-generator. * Optionally include empty directories from the CVS repository in the Subversion output. * More flexible keyword and EOL handling. * More aggressively omit unnecessary dead revisions. * Make check of illegal filename characters dependent on the target VCS. * Allow grafting a branch onto a parent that has itself been grafted. * Only require a DB module if the "internal co" functionality is used. (This dependency has been a source of much grief to people on systems without decent package managers.) * Sort using a Python implementation rather than an external sort command, to remove the dependency on POSIX-like sort. (This dependency has been the source of much grief to Windows users.) For more information see: http://cvs2svn.tigris.org/source/browse/cvs2svn/tags/2.4.0/CHANGES?view=markup You can get it here: http://cvs2svn.tigris.org/files/documents/1462/49237/cvs2svn-2.4.0.tar.gz The MD5 checksum is 4b93192e66302af9e537c6e33d80acc5. Please send any bug reports and comments to [email protected]. Michael -- Michael Haggerty [email protected] http://softwareswirl.blogspot.com/ ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1668&dsMessageId=3009456 To unsubscribe from this discussion, e-mail: [[email protected]]. ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3009457 To unsubscribe from this discussion, e-mail: [[email protected]].