[Top][All Lists]

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

RE: trouble with symlinks

From: Art
Subject: RE: trouble with symlinks
Date: Tue, 15 Jan 2002 10:56:52 -0600

> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf Of
> Simon Strandgaard
> Sent: Tuesday, January 15, 2002 9:36 AM
> To: address@hidden
> 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:

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.


> cvs co MODULE
> rm file
> ln -s /outside/FILE file
> edit /outside/FILE
> cvs com

reply via email to

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