Re: cvs editors funny

[Paul Sander]

No, it's not.  But in your last message you seemed rather upbeat about 
finding the path of the workspace having been squirreled away.  I'm 
just pointing out that you can't hope for a solution to this problem 
unless the workspace and repository can both agree on an identity for 
the workspace.  Comparing the present working directory of the client 
with a stored workspace path will likely not satisfy this requirement.  
Storing the present working directory of the client in the workspace at 
the time it was created, and using that stored value, would satisfy the 
requirement.

On Mar 30, 2005, at 7:08 AM, address@hidden wrote:

> Paul Sander wrote:
> > Be careful here.  The location appears to the directory
> > identified by
> > the client at the time the edit was done.  Due to network
> > mounts, this
> > path is not unique.  So when editing, unediting, or
> > committing a file,
> > there's really no way to know if the workspace you're affecting is
> > really the one recorded by a prior edit.
> True, but is that significantly different than the following scenarios:
>
> cvs co project
> cd project
> cvs edit file
> cd ..
> mv project proj2
>
> or:
> cvs co project
> cd project
> cvs edit file
> cd ..
> rm -rf project
>
> Or am I missing something?
>
> --
> Jim Hyslop
> Senior Software Designer
> Leitch Technology International Inc. ( http://www.leitch.com )
> Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )
--
Paul Sander       | "Lets stick to the new mistakes and get rid of the 
old
address@hidden | ones" -- William Brown