Re: failure to append to .cvspass should always be fatal

[Jim Meyering]

> Hmmm... I wonder if it is possible to come up with a sanity.sh test case
> for this one?

I considered it but, dismissed it as infeasible.
Of course, I would be happy to be proved wrong.

It might work to use a tool like subterfugue, where you could presumably
cause to fail the first write after the open-.cvspass-for-append.
But if you try to fill the disk containing .cvspass so that there's
enough room to rewrite that file, but not enough to append a few bytes
more, it probably won't be reliable.

I guess if you really insist, you might be able to do something
reasonably portable with expect and gdb.