[cvsnt] opposite of 'cvs export'?

[Aaron Kynaston]

What version of cvs is this for?

I've got cvsnt:

C:\>cvs version
Client: Concurrent Versions System (CVSNT) 2.0.0rc3 (client/server)
Server: Concurrent Versions System (CVS) 1.11.1p1 (client/server)

and import help returns:

Usage: cvs import [-d] [-k subst] [-I ign] [-m msg] [-b branch]
    [-W spec] repository vendor-tag release-tags...
        -d      Use the file's modification time as the time of
import.
        -k sub  Set default RCS keyword substitution mode.
        -I ign  More files to ignore (! to reset).
        -b bra  Vendor branch id.
        -m msg  Log message.
        -W spec Wrappers specification line.
(Specify the --help global option for a list of other help options)



Aaron Kynaston
akynaston at novell.com
office: (801) 861-6709
cell: (801) 368-8633
fax: (801) 861-6778
Novell Inc., The leading provider in net services software.
www.novell.com

>>> "Jerzy Kaczorowski" <jerzyk at wndtabs.com> 04/02/03 12:46PM >>>
> 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 
>

_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org 
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt