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>
<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><div><br></div><div>Thanks,</div><div>David C.</div><div><br><br></div><div><br><div class="gmail_quote">On Tue, Jul 6, 2010 at 10:13 AM, Marcus D. Hanwell <span dir="ltr"><<a href="mailto:marcus.hanwell@kitware.com">marcus.hanwell@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>This is now in, I combined the VTK and ParaView local hook instructions when both are missing to avoid a double error. Please let me know if you have any problems getting the hooks up and running.</div>
<div><br></div><font color="#888888">
<div>Marcus</div></font><div><div></div><div class="h5"><br><div class="gmail_quote">On Mon, Jul 5, 2010 at 2:18 PM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cool.<br>
<br>
Utkarsh<br>
<br>
On Mon, Jul 5, 2010 at 1:51 PM, Marcus D. Hanwell<br>
<div><div></div><div><<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>> wrote:<br>
> No, I already handled that (the check is disabled if CTest is driving the<br>
> build). This is already the case with VTK as of this morning, and it is<br>
> working well on the dashboards (but I will check the Nightly in the<br>
> morning).<br>
> Marcus<br>
><br>
> On Mon, Jul 5, 2010 at 1:46 PM, Utkarsh Ayachit<br>
> <<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>> wrote:<br>
>><br>
>> That sounds great. Of course, that would entail fixing all dashboard<br>
>> machines :).<br>
>><br>
>> Utkarsh<br>
>><br>
>> On Mon, Jul 5, 2010 at 1:10 PM, Marcus D. Hanwell<br>
>> <<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>> wrote:<br>
>> > Hi,<br>
>> > Please see the discussion about checking if developers have the local<br>
>> > git<br>
>> > hooks installed on the VTK developer list,<br>
>> > <a href="http://www.vtk.org/pipermail/vtk-developers/2010-June/008016.html" target="_blank">http://www.vtk.org/pipermail/vtk-developers/2010-June/008016.html</a><br>
>> > I intend to add similar checks to ParaView, but wanted to make ParaView<br>
>> > developers aware of the change too. At configure time you will be<br>
>> > prompted<br>
>> > to install local git hooks if they are not installed. You can disable<br>
>> > the<br>
>> > check, and it is automatically disabled if you are not using a git<br>
>> > clone, or<br>
>> > if the build is being driven by CTest.<br>
>> > This will ensure that all developers have hooks installed locally, for<br>
>> > more<br>
>> > information about the hooks please see,<br>
>> > <a href="http://www.vtk.org/Wiki/VTK/Git#Hooks" target="_blank">http://www.vtk.org/Wiki/VTK/Git#Hooks</a><br>
>> > Thanks,<br>
>> > Marcus<br>
>> > --<br>
>> > Marcus D. Hanwell, Ph.D.<br>
>> > R&D Engineer, Kitware Inc.<br>
>> > (518) 881-4937<br>
>> ><br>
>> > _______________________________________________<br>
>> > Paraview-developers mailing list<br>
>> > <a href="mailto:Paraview-developers@paraview.org" target="_blank">Paraview-developers@paraview.org</a><br>
>> > <a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
>> ><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
<br></blockquote></div><br></div>