Protections problem on CVS tree

Hi. I had ftp'd in all the files for the new ODBC code in the main
Postgres tree. I forgot to change the protection on the derived
odbc/configure file, so it is checked in without execute permission.

Do you have any experience fixing this kind of problem? Simply checking
in a new version with the right permissions doesn't seem to fix it. The
two alternatives I'm considering are:- "cvs delete" then "cvs add" the file with the right permissions- going into the
cvstree itself and brute-force change it
 

Suggestions? If you know what to do, and want to do it, feel free to fix
it. I'm inclined to try the brute-force method, but remote CVSup trees
(like mine) may need the same kludge fixup :O
                  - Tom