Inserting history after the facts?

[Arnout Standaert <ar...@student.kuleuven.ac.be>]

Hi list,

I'm losing count of the questions I'm firing in this direction, but 
anyway, here goes another one. As you may have noticed, I have some 
projects in CVS that I currently can't convert to SVN.

Let's say that I already start working in SVN, I just import the latest 
version of a project to a new SVN repo. So, this repo holds history 
starting from today. Then, assume that in 2005, I succeed in converting 
the current CVS repo to another SVN one, containing the history starting 
from the initial CVS import until today.

In that case, is it possible to efficiently join the two repositories, 
so that I get one big SVN repository, with a consistent history (ie, 
starting from initial CVS import until 2005 )?

Thanks in advance,
Arnout


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Inserting history after the facts?

["C. Michael Pilato" <cm...@collab.net>]

Ben Collins-Sussman <su...@collab.net> writes:

> On Fri, 2004-02-06 at 04:27, Arnout Standaert wrote:
> 
> > In that case, is it possible to efficiently join the two repositories, 
> > so that I get one big SVN repository, with a consistent history (ie, 
> > starting from initial CVS import until 2005 )?
> 
> Sure, it's possible.  You would need to dump the "later" repository, and
> then 'svnadmin load' it onto the end of the converted repository.  Of
> course, the revnums would change, so every working copy in the universe
> would be invalidated.
> 
> Hm, I also wonder if copyfrom-rev: arguments would be wrong...

Wow.  Hands waving so fast they're just a blur...   :-)

If it were just a simple matter of 'svnadmin load'ing a new dumpfile,
then copyfrom-rev arguments should be fine.  But it likely won't be
that easy.  If the older repos has a /trunk/tags/branches setup, and
the younger one does too (which, if you used cvs2svn on these CVS
repositories is the case) -- well, you're just begging for some kind
of name clashing to happen, at the very least in the /trunk, /tags,
and /branches directory themselves.

If you anticipate this scenario ever occurring, you'll want to setup a
repository with an alternate layout, such as /project/trunk,
/project/tags, /project/branches.  Heck, even if you lacked this
foresight, you could 'svn mkdir' and 'svn mv' your current layout into
such a new shape prior to loading the next dumpfile in.

Regardless, working copies of the first repo should be fine.  And your
mail leads me to believe that there'd be no working copies of the
latter repos yet because it was just created from a repos conversion
process.  But if there were, yeah, those folks would need to
re-checkout after the big merger.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Inserting history after the facts?

[Ben Collins-Sussman <su...@collab.net>]

On Fri, 2004-02-06 at 04:27, Arnout Standaert wrote:

> In that case, is it possible to efficiently join the two repositories, 
> so that I get one big SVN repository, with a consistent history (ie, 
> starting from initial CVS import until 2005 )?

Sure, it's possible.  You would need to dump the "later" repository, and
then 'svnadmin load' it onto the end of the converted repository.  Of
course, the revnums would change, so every working copy in the universe
would be invalidated.

Hm, I also wonder if copyfrom-rev: arguments would be wrong...



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org