-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan White <[EMAIL PROTECTED]> writes:
> On Thu, 29 Jul 2004, Mark D. Baushke wrote: > > > Dan White <[EMAIL PROTECTED]> writes: > > > > > The task manager has decreed that all > > > changes to all files will be checked in on a > > > daily basis. (Despite the attempted > > > reasoning about how CVS ain't built that > > > way) > > > > > > So, we need to have all files watched, and > > > set to notify the "Build Manager" role > > > account when folks edit, unedit, and commit. > > > > Your "Build Manager" sounds more like a > > micromanager. I hope there is a good reason > > for the process you have been told to follow. > > Your perception is right on the mark. The "good > reason" is 'cause he is the boss. There will likely be other jobs available if the economy in your area. You may wish to consider that not all managers are control fanatics... > > > I envisioned a cron script, run from the > > > build manager account that does a mass > > > checkout/watch on/watch add. But that > > > strikes me as criminally kludgy. > > > > > > Is there a better way to do it ? > > > > You probably only need to add new 'watch' > > statements as new files are added to the > > system. So, something that is wired into the > > 'loginfo' to look for new files and have them > > watched might be the way to go. > > > > I don't understand why a cron script would be > > needed... > > I'll explore that. Cron was considered as a > brute-force approach. Hmmm... the point is that I do not understand what you intended to do with your cron job. > "If brute force does not work, it is only > because it is being applied in an insufficient > quantity." > > Thanks. Good luck, -- Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFBCTs53x41pRYZE/gRAlrqAJ4uQdH/qD1OFf+RXpBHv6d5JdMPmgCfcjab 832d/3qbUgJqxf1rUwJxoBQ= =+UYR -----END PGP SIGNATURE----- _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs