Michael K. W. Wong writes:
>
> will show the file status is dead. However, if Developer A updates a.C
> and commits his changes (which is all legal in 1.10), the file now has a
> status of Exp even though it resides in the Attic directory.
That's definitely a bug in CVS. Update tries to do a merge and always
gets conflicts; it should probably detect the dead file and issue a
message, but then what? Should it do a merge? Should it make the file
appear to be newly-added so that a commit would correctly resurrect it?
Should it just leave the file alone so that it stays out-of-date?
What do people think?
-Larry Jones
I hope Mom and Dad didn't rent out my room. -- Calvin
