On Tue, 2003-03-04 at 20:14, Daniel Rall wrote:
> Garrett Rooney <rooneg@electricjellyfish.net> writes:
>
> > Eric Hopper wrote:
> >
> > >Perhaps someone with commit access might want to consider doing:
> > >
> > >svn rm http://svn.collab.net/repos/svn/trunk/tools/cvs2svn/rcsparse/CVS
> > >
> > >*grin*,
> >
> > actually, that's intentional. karl checked in his CVS working copy,
> > so that when we later want to update to a newer version of rcsparse,
> > it's as simple as 'cvs up', make sure it works, 'svn commit'.
>
> Darn it, that's a neat trick which is going to stop working when
> rcsparse switches from CVS to Subversion!
No, it won't stop working. Much the same effect can be achieved with
the svn:externals property. In some ways, it won't be _quite_ as nice,
but it will be almost as nice. :-) I'm not sure if you can specify a
specific version of a repository in an svn:externals declaration, but if
you can, I can't see a huge different.
I thought it may have been a mistake at first because 'compat.py' wasn't
under CVS control.
Have fun (if at all possible),
--
Eric Hopper <hopper@omnifarious.org>
Omnifarious Software
Received on Wed Mar 5 19:41:42 2003