> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Simon Strandgaard > Sent: Tuesday, January 15, 2002 9:36 AM > To: [EMAIL PROTECTED] > Subject: Re: trouble with symlinks > > > Yes this is exactly what i have done, so i can edit my files from DOS.
In this case, I would also like to preserve the current behaviour as the default. Perhaps a switch could accommodate your need, but I would consider the "critical information" as the "link" not the source, in the context of my "Version Control" usage. I.e., I would like CVS to handle symlinks just like tar does, which does have a derencing switch to do what you are trying to do. I.e., I would consider the lost of a "link" as a loss of information in most cases. I just tried this under Cygwin and cvs import would not import symlinks. I.e, I created: test.c test2.c -> test.c it reported: N test2/test.c L test2/test2.c So, it didn't even import the symlinks. In this case, I'd just cd to the DOS directory and create a CVS module to manage those files directly and create a "mklinks" file in the Unix tree to re-establish my symlinks when I checked out that module a fresh. Art > cvs co MODULE > cd MODULE > rm file > ln -s /outside/FILE file > edit /outside/FILE > cvs com http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
