Stephen Rasku writes:
>
> $ mv umoproc.cpp umoproc.cpp.save
> $ cvs rm
> cvs remove: Removing .
> cvs remove: file `Makefile.pkg' still in working directory
> cvs remove: scheduling `umoproc.cpp' for removal
> cvs remove: use 'cvs commit' to remove this file permanently
> cvs remove: 1 file exists; remove it first
> $ mv umoproc.cpp.save umoproc.cpp
> $ cvs add umoproc.cpp
> cvs add: umoproc.cpp should be removed and is still there (or is back
> again)
That's the way it's supposed to work. When you've removed a file and
haven't committed the removal, doing a ``cvs add'' resurrects the file
from the repository, which it can't do in this case because there's
another file in the way. Either do a commit before the mv or do the mv
after the add.
-Larry Jones
I hate it when they look at me that way. -- Calvin
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
