----- Original Message ---- > From: Marcus (OOo) <[email protected]> > Am 07/18/2011 04:31 PM, schrieb BRM: > > ----- Original Message ---- > > > >> From: Marcus (OOo)<[email protected]> > >> Am 07/14/2011 09:59 PM, schrieb Dave Fisher: > >>> (1) Get the existing svn website repository into the project's svn. I >think > >> we should just export it all and then add to the project. The move from >cvs to > >> svn in kenai has apparently lost all prior history. Do we care? If > >> exports >are > >> fine then we can proceed. > >> > >> Yes, history is lost. Here is an example on a file that was imported > >> into Kenai's SVN repo: > >> > >> r1 | kenaiadmin | 2011-02-23 15:51:43 +0100 (Wed, 23 Feb 2011) | 1 line > >> > >> initial import > >> > >> So, when we import the Kenai SVN into the Apache SVN then commit history > >> is not important as we will loose data from February until today. > >> > >> At least, that's my opinion. > >> > > > > FWIW - there is a project cvs2svn that can convert CVS/RCS into SVN dumps >that > > can then be loaded with full version history. > > > > You can find it here: http://cvs2svn.tigris.org/ > > > > If the CVS used previously was CVSNT or another variant that had some > > extensions, then it would be useful to lend them a hand with the support for > > that CVS variant (or completing the CVSNT support). > > Their resources are extremely limited but it is generally doable. > > > > So, all is not necessarily lost - but it does depend on whether you want to > > reload the SVN repo. > > I don't know how you thought about CVS but the respective repo is > already on SVN. >
I am just noting that if you all cared about the history then there is a way to get it given the previous repository, responding to what I quoted which mentioned CVS. I believe cvs2svn also supports several other repository systems; for example, they also have a cvs2git tool. It may be of interest to keep the history, but in a secondary repository for archival/research purposes - again, supposing it is available. Or you can do the following: 1. Build the history 2. Rename the existing repository 3. Load the existing history into a new repository 4. Dump the existing repository history 5. Load the existing repository history into the new repository as well. The 'svnadmin' tool has a great functionality - you can load multiple SVN Dumps into the same repository, and there are tools to make adjustments in both it and the cvs2svn tools - e.g. in case the tree names changed. I would caution though, that the it will take a good amount of time to do step #2 above - the larger the dump file the longer it takes to load in. So to recap, all I am saying is that it is possible to recover the history if the community desired to do so; and that it may even be possible to do so while keeping the existing changes since the existing SVN repository was setup. Now, if it's of no interest to the community, then fine. This will just be a footnote in the mailing list. As always, $0.02 Ben
