Our practice when generating a directory tree for later population is to put
in a readme file describing the intent and later update it to describe the
reason for the directory to exist and the files contained in it.
Our philosophy has been, if you can't articulate the reason for something
then you don't need it.
Mike.
-----Original Message-----
From: Anders Truelsen [mailto:[EMAIL PROTECTED]]
Sent: March 22, 2001 2:57 PM
To: 'Fisher, Shane'; '[EMAIL PROTECTED]'
Subject: RE: Import not working recursively
Try putting some files in the subdirectories, .cvsignore for example.
That should make a difference.
regards
/anders
> -----Original Message-----
> From: Fisher, Shane [mailto:[EMAIL PROTECTED]]
> Sent: 22. marts 2001 20:37
> To: '[EMAIL PROTECTED]'
> Subject: Import not working recursively
>
>
> When I follow the example from the Cederqvist manual where
> you create a
> directory tree from scratch, I find that CVS only creates the
> project at the
> topmost hierarchy. For example:
>
> $ mkdir tc
> $ mkdir tc/man
> $ mkdir tc/testing
> $ cd tc
> $ cvs import -m "tc project creation" tc tc tc_1_1
>
> $ cd /tmp
> $ cvs co tc
> cvs server: Updating tc
>
> $ ls tc
> CVS
>
> ???
>
> Shane M. Fisher
> AT&T Wireless Services
> Developer II, Marketing IT
> *[EMAIL PROTECTED]
> *425 580 6648
> *425 501 1494 (cell)
>
>
> _______________________________________________
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
