Updating when the local sandbox already has the new directory

[Matthew Doar]

If I run "cvs update -d" to make sure I get a new directory "newdir"
from the repository into my sandbox, but I already happen to have
already created "newdir" locally, I was surprised that I didn't get a
"move newdir out of the way" message - just "? newdir". I seem to be
able to commit files in newdir, though cvs diff continues to give me "?
newdir" output.

Is this expected behaviour? 

When branches are introduced into the issue, adds and commits seemed to
add directly to the Attic.

~Matt

Detailed instructions to reproduce this:

User B

cvs co test
cd test
mkdir newdir
(newdir *not* added to cvs)

User A 

cvs co test
cd test
mkdir newdir
cvs add newdir
cd newdir
edit foofile
cvs add foofile
cvs commit

User B

cvs update -d

--> Gets output about "? newdir" but no warning to remove newdir

Environment: cvs server 1.11.5, cvs client 1.12.1.1, both Linux RH 8.0