Alexander L. Belikoff wrote:
>>If you don't need history, a straight 'svn import' of your dataset
>>should prove easy and fast. But it's not clear whether you tried that.
>>Maybe that's just not an option for your project, dunno.
>
> We do need history. As do most of the development groups out there. Cases
> where people can happily toss their history and start afresh are fairly
> exotic and should be treated as such. Just ask some development group
> whether they would be comfortable to prune their repository to the existing
> version only. :-)
We won't be converting our cvs repository to svn as we don't want to
transfer the history. When we changed to cvs we ported the history from
PVCS (was almost identical to RCS then) and didn't find it very useful
as we had to keep the old PVCS copy anyway. If anyone needs to look at
the history of a file it will be easy to find in cvs and with viewcvs
both can be seen from the same web interface.
We have build instructions for all our products which up to now have
been in cvs, for those to work we have to keep the cvs repository. Over
time, the cvs repository has become a little messy with branches off
branches etc., converting to svn is an opportunity to clear up some of
this mess.
We will however move enough history by hand so that product versions
which are under active maintenance are in svn. This is a little time
consuming, but is a lot faster than cvs2svn!
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 22 11:05:02 2004