Nope. The contrary would be what i'd be looking at - have an
EXIT_FAILURE when your tag ain't there (mistyped or deleted)
even though it's in the val-tags list.
What i was thinking of, is to have this return code when cvs checks out (or rdiffs) the module and
finds out in the end that no files were send across the wire. To check it preliminary would be a big waste of time -
this would somewhat erase the benefits of the val-tags file.
I recon this would have to be implemented as a counter or flag that increases
or is set once a file is found with the provided tag.
Of course the better the return codes from cvs are, the better you can automate
your buildprocess - so
as a developer i'd appreciate any effort in that direction. For the time being
though it would be sufficient for us
to have it return EXIT_SUCCESS & EXIT_FAILURE correctly (or as we'd be
expecting it if you want).