In this case IMHO we should not nag the project mailing list but the committer that has done the commit, so he has time to revert or fix it.
Project nags IMHO should be done only from the main Forrest clean-run.
Not sure nagging the commiter from gump is a good idea when all the dependencies are shifting underneath.
I think if instead we nag the list but include
a list of cvs changes
a list of projects that we depend on that have changed.
Perhaps gump could include a CVS changes page with a link the the cvsweb view of the diffs for each change.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
