> We've run into situations where a pre or post update would be very useful.
> Basically we include "special" instructions in each commit log. The
> special instructions might be something like "update to latest version of
> some tool or library" before running the build. If someone is on holidays
> (for example) and updates 20 or 30 revisions, it's a huge pain to have to
> go through old logs to verify the existence of special instructions. With
> a pre or post update hook, we could trigger an email that would tell a
> user that in the 20 revisions they just applied they missed some special
> instructions.
>
> Since a framework already exists for hooks, it would be great to simply
> extend that framework to include a pre or post update hook.
>
> Eoin Dunne
>
>
> Confidentiality Notice: The information in this e-mail may be confidential
> and / or privileged. This e-mail is intended to be reviewed by only the
> individual or organization named in the e-mail address. If you are not the
> intended recipient, you are hereby notified that any review, dissemination
> or copying of this e-mail and attachments, if any, or the information
> contained herein, is strictly prohibited.
>
>
Received on Fri Oct 1 00:25:44 2004