will be able to interpret 93
ou 98 befunge code...
I'm sorry, 'cause I know cvs does not handle very well directory
renaming.
This seems to be a good idea. I'd commit it, except that it needs more
than commit access to move a directory with CVS. Who has enough shell
access to cvs.perl.org to do
, and the same interpreter will be able to interpret 93
ou 98 befunge code...
I'm sorry, 'cause I know cvs does not handle very well directory
renaming.
This seems to be a good idea. I'd commit it, except that it needs more
than commit access to move a directory with CVS. Who has enough shell
access
On Fri, Nov 29, 2002 at 10:14:39AM -0800, Robert Spier wrote:
Nicholas Clark writes:
This seems to be a good idea. I'd commit it, except that it needs more
than commit access to move a directory with CVS. Who has enough shell
access to cvs.perl.org to do this? [assuming it does want to be
Would it also be your job to do porting of subversion to VMS, so that we
could consider replacing CVS with something that lets clients do directory
moves? :-)
Sadly, no. :)
But I can tell you that I am actively investigating the use of
subversion for future use on perl.org projects. We're
know cvs does not handle very well directory
renaming.
Thanks,
Jerome
--
[EMAIL PROTECTED]
