[cvsnt] opposite of 'cvs export'?

[Jerzy Kaczorowski]

> I have developers who have imported all of their local source code (cvs
> import'ed), and wonder why their code isn't 'connected' to cvs.

There is a -C option for the import command that creates the sandbox:

cvs -H import
Usage: cvs import [-C] [-d] [-k subst] [-I ign] [-m msg] [-b branch]
    [-W spec] repository vendor-tag release-tags...
        -C      Create CVS directories while importing.
        ...(snip)

Best Regards,
Jerzy

----- Original Message -----
From: "Aaron Kynaston" <akynaston at novell.com>
Newsgroups: support.cvsnt
To: <cvsnt at cvsnt.org>
Sent: Thursday, April 03, 2003 1:26 AM
Subject: [cvsnt] opposite of 'cvs export'?


> Hey all, I've run in to an interesting situation.
>
> I have developers who have imported all of their local source code (cvs
> import'ed), and wonder why their code isn't 'connected' to cvs.
>
> They forgot that they have to 'cvs co' to create their sandboxes and get a
> version that CVS can handle.
>
> I would very much like the ability to generate from CVS **ONLY** the CVS
> directories . . like exactly the opposite of a 'cvs export'.  That way,
> they'd simply be able to move the directory structure of CVS dirs on top
> of their local directories, and then do a cvs up to continue to ensure
> that no files were ignored ect.
>
> Any one have an idea?
>
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
>