I'd like to provide an example of a case where something like this would be
useful. I want to prevent people from building a program that was compiled
with 2 different versions of a C++ header file. We already use the cvs
ident command to look for problems like this, but it would be even better
Have you considered something like this?
Create a special target in your makefile that performs all the auditing
of your process that you want. Its prerequisites should be all of the
header files you're concerned about. Put it under CVS control and commit it
with all of your sources, and apply
Title: Modify files on before commit using loginfo?
Hi,
Is it possible to modify the files before they are commited to the repository using loginfo or commitinfo?
How should I do this?
Is there a file stream I can read and write to?
Or should I do this via CVS commands (checking out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
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
