info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Import source code from a CVS to another CVS


From: Mark D. Baushke
Subject: Re: Import source code from a CVS to another CVS
Date: Fri, 28 Mar 2008 09:08:59 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Spiro Trikaliotis <address@hidden> writes:

> * On Thu, Mar 27, 2008 at 11:46:18PM -0700 Mark D. Baushke wrote:
>  
> > If you do a 'cvs import' in a tree which has a CVS directory, the CVS
> > directory and all of its contents is ignored completely.
> 
> Is this true even if you perform a "cvs import -I!"?

Yes. CVS will always ignore the CVS directory as a CVS directory inside
of the repository is used for cvs edit and cvs watch related control
files.

This should work fine with cvs 1.11.22 and cvs 1.12.13. There may have
been more ancient releases of CVS which did not do the same thing, but
I do not recall which ones those would have been.

> I would never use import without that -I! switch...

I understand. I tend to use 'cvs import -I ! -ko -d -X' myself, so that
files are only on the vendor branch with the original datestamp and
without normal cvs keyword expansion. In some cases, I would then go in
with cvs admin and change the -ko to a -kb for the small binary files
(e.g., .jpg and .png and *.pdf) that might have come along for the ride
and need to be binary to work properly for non-UNIX checkouts.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFH7RgbCg7APGsDnFERArKGAJ9asz5adEJ4D4ScLSFygLnqxREn3wCeNyEo
HQUEHjPi0OZBoneRKsCtLoA=
=PKTv
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]