<div class="gmail_quote">On Tue, Jul 6, 2010 at 3:27 PM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Now that we've had much discussion about whether to have the hooks at all... time for the next question.<div><br></div><div>If the hooks are changed in the master repository, how are those changes going to be propagated?</div>
</blockquote><div><br></div><div>I am looking into a couple of possibilities right now. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><br></div><div>The check for the hooks is just whether there exists a git repo in the .git/hooks directory, not what it contains...</div><div><br></div><div>Any thoughts on how to make the hooks change-able so that when changes are made to the master repo, they get propagated correctly? Or, at least, that I get notified that my hooks are out of date and instructions on how to update them manually....?</div>
<div><br></div></blockquote><div>It is certainly a concern, and I am hoping to add some checking along with some useful aliases. I will hopefully have something more concrete very soon, but need to do a little more testing first.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Marcus</div></div>