Just FYI, folks:
We've re-prioritized a bit, and so Mike is putting off the cvs2svn
work in order to get the svn code to M3 readiness. We simply realized
that, with Subversion this close, him suddenly leaving it and pouring
his energies into cvs2svn would be a huge momentum sink, not just for
him, but for others who are accustomed to his responsiveness about
Subversion issues. (Not to mention the tandem coding he does with Ben
and me a lot.)
-K
"Justus Pendleton" <subversion@ryoohki.net> writes:
> cmpilato@collab.net writes: > Other ideas that have been tossed around
> include a
> > using a Perl or Python RCS-parsing module.
>
> You may want to look into vcp, which gets mentioned on the perforce
> user's mailing list every now and again. I haven't used it myself
> but: "vcp (and the Perl module VCP.pm) is a system for copying
> resources under version control from one repository to another,
> possibly different, repository, or to/from RevML. Directory trees may
> be re-rooted, and only particular changes need be copied (or all can
> be copied)." Right now I believe it supports CVS and perforce. If it
> can already suck in a CVS repository then you've already got half the
> work done for you :-)
>
> The module is on CPAN so you can just do $ perl -MCPAN -eshell
> cpan> install VCP Justus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:33 2006