[Please forgive me for spamming multiple mailing lists. Followups
please to dev_at_cvs2svn.tigris.org.]
I would like to announce that on 8 September our second child, a son
named Phillip, was born. He was a bit premature and had to spend 2.5
weeks in the hospital, but he is home now and both baby and mother are
This means that the time I have available to hack on cvs2svn/cvs2git
will shrink to very close to zero. I am very happy that other people
have been answering user emails recently on the mailing lists and hope
that that will continue. If other people step forward to handle bug
reports that would be great.
I see the following as the highest priorities for the near future of
1. Fix problems in the test suite caused by upstream changes in svntest.
I will discuss this problem in a separate email.
2. Make a release 2.2 containing the improvements that have been
accumulating on trunk. See  for a fairly up-to-date summary of
3. Give Johan Herland as much encouragement and support as possible to
get involved with the cvs2svn project :-). Johan has worked on his own
company-internal "cvs2git" converter called ConVerSion2Git that has a
lot in common with cvs2svn, and he has expressed interest in
collaborating with us (and has already submitted a few patches, thanks!)
4. Try to encourage people from the git, hg, and bzr communities to
test, use, and contribute improvements to cvs2svn so that it becomes
more useful as a tool to convert to those DVCSs. All three of them have
"fast-import" extensions that in principle consume data formatted in the
"git-fast-import" format , but the extensions are in various levels
of maturity and all have quirks that might have to be accommodated by
cvs2svn. And the documentation and user interface for converting to
non-SVN VCSs is still pretty primitive. Finally, a certain amount of
evangelizing would help. People have to understand that most other
tools are in fact broken!
5. Improve our branding as a universal "cvs2xxx" converter that can
convert to multiple destination systems. I haven't heard any really
good suggestions for a new project name; other suggestions are welcome.
So far I have been using "cvs2svn", "cvs2git", and "cvs2hg" to refer to
three of its incarnations, and one approach might be to claim the entire
"cvs2*" namespace. But for project branding, it would probably be
better to come up with a new overarching project name to help people
understand that a single tool is being talked about. I also have no
idea what has to be done at tigris.org to get the project renamed;
perhaps somebody could look into it?
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-28 07:35:13 CEST