Re: [SVN-MIGRATION] Proposed repository structure

My suggestion is to import everything to SVN, and then keep the  
tarball of the entire CVS repo somewhere.  This tarball could  
potentially also live in a corner of the SVN tree.

--Wez.

On Sep 2, 2008, at 4:21 PM, Johannes Schlüter wrote:

> On Tue, 2008-09-02 at 14:20 +0200, Marcus Boerger wrote:
>> 5) No parallel CVS supported integrated into the SVN repository. A
>> gateway that can access SVN Data in a CVS way is nice to have. The
>> easiest way is a cronjob that does snapshots into a readonly CVS
>> repository.
>
> I don't see a point in keeping a cvs service at all, nowadays all
> systems should have (access to) a SVN client, that might have been
> different when SVN was first introduced and might not be true for
> systems like git but for SVN there's no need for additional admin work
> in this times. The only question is whether to import everything  
> (while
> I think everybody agrees to that) and where to keep the RCS ,v files  
> for
> archaeologists :-)