Brian Moore <mooreb@epinions-inc.com> writes:
> i suspect that even if subversion can be self-hosted, that doesn't
> mean that there can't be a cvs server running in parallel with the
> subversion server. i'm thinking that the cvs served tree is read-only,
> while actual development occurs in the subversion served tree.
That sounds like a great idea! (As long as it isn't too much of a
drain on resources to set it up.)
-K
> there could be a svn2cvs script that runs periodically to this end.
> i think that it would be acceptable to say that the cvs tree is
> slightly out of date (longer than 24 hours would prolly be
> unacceptable). the largest problem is going to be build breakage or
> crashers in the cvs served tree that get more fixed more quickly in
> the subversion served tree.
>
> anyway, i agree with daniel, that if providing svn2cvs turns out to be
> painful, we can just provide automatically generated source tarballs.
>
> b
>
> On Mon, 14 May 2001, Daniel Stenberg wrote:
>
> > Hi guys
> >
> > I know M3 includes SVN being self-hosted, with the SVN sources within SVN
> > itself.
> >
> > Have anyone put any thoughts on doing some kind of duplicate storage in both
> > CVS and SVN (like a script that takes the comments and commits in both
> > systems)?
> >
> > It would:
> >
> > a) reduce the amount of troubles for newcomers that have CVS clients
> > installed locally and want to get the SVN source. Otherwise, they'll have
> > to fetch a tarball/binary first, only to install a SVN client and then get
> > the source to re-install the client (and possibly the server).
> >
> > b) offer the reliability of CVS in case something in SVN would blow up
> >
> > Possibly, (a) can be substituted by automaticly generated tarballs or
> > something.
> >
> > --
> > Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
> > ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:30 2006