[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: CVS Checkout with the Subversion cmdline client :)

From: Jay Freeman \(saurik\) <saurik_at_saurik.com>
Date: 2002-08-03 16:26:50 CEST

----- Original Message -----
From: "William Uther" <will+@cs.cmu.edu>
To: "Jay Freeman (saurik)" <saurik@saurik.com>; "svn-dev"
<dev@subversion.tigris.org>
Sent: Thursday, August 01, 2002 7:36 PM
Subject: Re: CVS Checkout with the Subversion cmdline client :)

...
> I was just chatting on #svn and saying it would be cool if svn:externals
> could access CVS repositories. Then Jay mentioned that you could use his
> WebDAV<->CVS gateway to get something close to that effect.
>
> The gateway has a few limitations right now: can't handle updates, and
must
> be run with local access to the CVS repos. But it I think this is an
> interesting approach (ok, ok: sick, twisted and interesting). :)
>
> Later,
>
> \x/ill :-}

I've actually managed to get update somewhat working :) :). It doesn't yet
handle removing files correctly, but I'm really close (just way too tired...
now 7:25AM, been working on this all night). I'm not 100% sure how it
handles modifications to directory structure either. Really I've only
tested adding files and changing their contents within the root directory,
and that works. Oh... I forgot about reviving a file... I bet that won't
work. You can't ask for old revisions yet, you can only update to HEAD.
This makes it difficult for me to setup a public server to demonstrate with
:). Below is a log of a session that switches back and forth between CVS
and Subversion.

Note that the insanely large version numbers you see are because I model
repository wide revisions with CVS using a timestamp expressed as the number
of seconds since 1970. This makes the repository pretty close to
continuous. The HEAD is always considered to be _now_. You can spend the
rest of the day just hitting "svn up" and getting back a repository that is
a few seconds newer. Considering the emphatic arguments from people on this
mailing list that revision numbers aren't something users should really be
dealing with anyway, it shouldn't matter that I have truly destroyed a
user's ability to even think about them, right? :P

Sincerely,
Jay Freeman (saurik)
saurik@saurik.com

C:\Thrash\Dv>cvs -d :pserver:saurik@cvs.saurik.com:/cvs/ninetjer co test
cvs server: Updating test

C:\Thrash\Dv>cd test

C:\Thrash\Dv\test>echo hello 1>bob

C:\Thrash\Dv\test>cvs add bob
cvs server: scheduling file `bob' for addition
cvs server: use 'cvs commit' to add this file permanently

C:\Thrash\Dv\test>cvs commit -m ""
cvs commit: Examining .
RCS file: /cvs/ninetjer/test/bob,v
done
Checking in bob;
/cvs/ninetjer/test/bob,v <-- bob
initial revision: 1.1
done

C:\Thrash\Dv\test>cd ..

C:\Thrash\Dv>svn co http://www.saurik.com/cvs-bin/
A cvs-bin/bob
Checked out revision 1028384179.

C:\Thrash\Dv>type cvs-bin\bob
hello

C:\Thrash\Dv>cd test

C:\Thrash\Dv\test>echo change 1>bob

C:\Thrash\Dv\test>cvs commit -m ""
cvs commit: Examining .
Checking in bob;
/cvs/ninetjer/test/bob,v <-- bob
new revision: 1.2; previous revision: 1.1
done

C:\Thrash\Dv\test>cd ..\cvs-bin

C:\Thrash\Dv\cvs-bin>svn up
U ./bob
Updated to revision 1028384186.

C:\Thrash\Dv\cvs-bin>type bob
change

C:\Thrash\Dv\cvs-bin>cd ..\test

C:\Thrash\Dv\test>echo extra 1>lots

C:\Thrash\Dv\test>cvs add lots
cvs server: scheduling file `lots' for addition
cvs server: use 'cvs commit' to add this file permanently

C:\Thrash\Dv\test>cvs commit -m ""
cvs commit: Examining .
RCS file: /cvs/ninetjer/test/lots,v
done
Checking in lots;
/cvs/ninetjer/test/lots,v <-- lots
initial revision: 1.1
done

C:\Thrash\Dv\test>cd ..\cvs-bin

C:\Thrash\Dv\cvs-bin>svn up
A ./lots
Updated to revision 1028384192.

C:\Thrash\Dv\cvs-bin>type lots
extra

C:\Thrash\Dv\cvs-bin>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 3 16:30:09 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.