Agreed. Make the user make the change you want committed. Supply a script to do it if necessary. Then use the *info capability to verify that it was done.
>--- Forwarded mail from [EMAIL PROTECTED] >Anders Carlberg <[EMAIL PROTECTED]> writes: >> Is it possible to modify the files before they are commited to the >> repository using loginfo or commitinfo? >At loginfo time it is already too late, the file has been committed to >the repository. At commitinfo time, you have access to the server side >copy of the files (or the original files if in :local: mode), so it may >be possible to whack in changes. Doing so is a very bad idea as it >introduces entropy that is not controlled by the user into the process >of trying to accurately record the state of files that 'worked' for the >user. >> How should I do this? >You should not do it. If you choose to do it, you may find yourself >in a world of hurt eventually. >> Is there a file stream I can read and write to? >Not really. >> Or should I do this via CVS commands (checking out and commit) (but then >> the files get a new version? Or?) ? >CVS is bright enough not to provide for this kind of lunacy/idiocy. >> Is there anyone that has done something like this? >Probably, folks have been abusing CVS in ways it was never intended to >be used for many years now. This does not make it a good idea. >--- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
