You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Alain Mellan <al...@st.com> on 2002/10/29 20:56:58 UTC
CVS import?
Hi,
I was reading the documents and book about SVN, because I'm considering
switching to SVN from CVS. I haven't seen anywhere the mention of a
migration path for a CVS repository. Surely, if you guys want to replace
CVS, you thought about it, right?
Now that I think of it, it might not be as easy as it seem, if we want
to preserve the whole history, tags, etc.
What are your plans?
Thanks in advance.
-- alain.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
[PATCH] FAQ for cvs2svn conversion (was Re: CVS import?)
Posted by Benjamin Pflugmann <be...@pflugmann.de>.
On Tue 2002-10-29 at 20:42:39 -0600, B. W. Fitzpatrick wrote:
>
> Benjamin Pflugmann <be...@pflugmann.de> writes:
> > But part of the original point still stands: There seems to be no
> > obvious hint in the documentation on how to migrate from CVS.
[...]
> > Else, maybe there should be some information in the README or on the
> > web site?
>
> I think this is a great idea for a FAQ. If you can take a minute to
> write up something and submit a patch, I'll see to it that it makes
> its way into the repository.
I am quite bad at writing documentation (English or not, but writing
in English surely doesn't help). But since I insisted on the point, I
will at least try. You'll find the result below.
Regards,
Benjamin.
Patch from Benjamin Pflugmann <be...@pflugmann.de>
* www/project_faq.html (cvs2svn): New question answered
Index: www/project_faq.html
===================================================================
--- www/project_faq.html
+++ www/project_faq.html 2002-10-30 12:21:31.000000000 +0100
@@ -36,6 +36,8 @@
<li><a href="#co-svn">How do I check out the Subversion code?</a></li>
<li><a href="#repository">How do I create a repository? How do I
import data into it?</a></li>
+<li><a href="#cvs2svn">How do I import an existing CVS repository
+ into Subversion?</a></li>
<li><a href="#proxy">What if I'm behind a proxy?</a></li>
<li><a href="#paranoid">My admins don't want me to have a HTTP server for
Subversion. What can I do if I still want remote usage?</a></li>
@@ -295,6 +297,16 @@
<![CDATA[-----------------------------------------------------------]]>
+<h3><a name="cvs2svn">How do I import an existing CVS repository
+into Subversion?</a></h3>
+
+There is no tool ready to do that. You may want to check out
+<tt>cvs2svn.py</tt> in <tt>tools/cvs2svn.py</tt>, which is still under
+work. It is not officially supported, so use it on your own risk. Be
+sure to read the <tt>README</tt> in the same folder.
+
+<![CDATA[-----------------------------------------------------------]]>
+
<h3><a name="proxy">What if I'm behind a proxy?</a></h3>
<p>The Subversion client can go through a proxy, if you configure it
Re: FAQ for cvs2svn conversion (was Re: CVS import?)
Posted by Greg Stein <gs...@lyra.org>.
On Tue, Oct 29, 2002 at 08:42:39PM -0600, B. W. Fitzpatrick wrote:
>
> Benjamin Pflugmann <be...@pflugmann.de> writes:
> > But part of the original point still stands: There seems to be no
> > obvious hint in the documentation on how to migrate from CVS. I
> > remember that when I started evaluating svn (r2847, IIRC), I already
> > had compiled it and poked around with the code, but still did not knew
> > how to convert from CVS. I learned it some week later, when cvs2svn
> > was mentioned on this list.
> >
> > Ignore me, if I am simply out of date or missed the obvious and this
> > is already documented (but then, where?).
> >
> > Else, maybe there should be some information in the README or on the
> > web site?
>
> I think this is a great idea for a FAQ. If you can take a minute to
> write up something and submit a patch, I'll see to it that it makes
> its way into the repository.
Yes, it would be good for a FAQ.
The reason it hasn't really been doc'd anywhere is that the tool isn't done.
Read: not supported / use at your own risk :-)
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: CVS import?
Posted by Kevin Pilch-Bisson <ke...@pilch-bisson.net>.
On Tue, Oct 29, 2002 at 10:48:20PM +0100, Benjamin Pflugmann wrote:
> Hello.
>
> On Tue 2002-10-29 at 16:08:42 -0500, Garrett Rooney wrote:
> > Alain Mellan wrote:
> > >Hi,
> > >
> > >I was reading the documents and book about SVN, because I'm considering
> > >switching to SVN from CVS. I haven't seen anywhere the mention of a
> > >migration path for a CVS repository. Surely, if you guys want to replace
> > >CVS, you thought about it, right?
> > >
> > >Now that I think of it, it might not be as easy as it seem, if we want
> > >to preserve the whole history, tags, etc.
> > >
> > >What are your plans?
> >
> > check out cvs2svn.py in tools/cvs2svn.
>
> But part of the original point still stands: There seems to be no
> obvious hint in the documentation on how to migrate from CVS. I
> remember that when I started evaluating svn (r2847, IIRC), I already
> had compiled it and poked around with the code, but still did not knew
> how to convert from CVS. I learned it some week later, when cvs2svn
> was mentioned on this list.
>
> Ignore me, if I am simply out of date or missed the obvious and this
> is already documented (but then, where?).
>
> Else, maybe there should be some information in the README or on the
> web site?
>
I think the reason that there isn't such documentation right now is because
the script isn't complete, and we're still working on making the bindings
easier to build. Even still though, maybe there should be a pointer to
cvs2svn, just with a big warning on it.
What do others think?
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson http://www.pilch-bisson.net
"Historically speaking, the presences of wheels in Unix
has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: CVS import?
Posted by Benjamin Pflugmann <be...@pflugmann.de>.
Hello.
On Tue 2002-10-29 at 16:08:42 -0500, Garrett Rooney wrote:
> Alain Mellan wrote:
> >Hi,
> >
> >I was reading the documents and book about SVN, because I'm considering
> >switching to SVN from CVS. I haven't seen anywhere the mention of a
> >migration path for a CVS repository. Surely, if you guys want to replace
> >CVS, you thought about it, right?
> >
> >Now that I think of it, it might not be as easy as it seem, if we want
> >to preserve the whole history, tags, etc.
> >
> >What are your plans?
>
> check out cvs2svn.py in tools/cvs2svn.
But part of the original point still stands: There seems to be no
obvious hint in the documentation on how to migrate from CVS. I
remember that when I started evaluating svn (r2847, IIRC), I already
had compiled it and poked around with the code, but still did not knew
how to convert from CVS. I learned it some week later, when cvs2svn
was mentioned on this list.
Ignore me, if I am simply out of date or missed the obvious and this
is already documented (but then, where?).
Else, maybe there should be some information in the README or on the
web site?
Regards,
Benjamin.
Re: CVS import?
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Alain Mellan wrote:
> Hi,
>
> I was reading the documents and book about SVN, because I'm considering
> switching to SVN from CVS. I haven't seen anywhere the mention of a
> migration path for a CVS repository. Surely, if you guys want to replace
> CVS, you thought about it, right?
>
> Now that I think of it, it might not be as easy as it seem, if we want
> to preserve the whole history, tags, etc.
>
> What are your plans?
check out cvs2svn.py in tools/cvs2svn.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org