[cvsnt] opposite of 'cvs export'?

[Kari Hoijarvi]

Could they check out to a different folder and copy their modified files
over?

I'd recommend a meticulous code review with a visual difference tool before
checking in, though.

Kari

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Aaron Kynaston
Sent: 02 April 2003 11:26
To: cvsnt at cvsnt.org
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