<HTML>
<HEAD>
<TITLE>Re: [Paraview-developers] [vtk-developers] New git commit hooks</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Veering slightly off the main topic, could we get some guidance on the minutia that we are expected to follow when coding and committing changes to VTK, ParaView, etc.? Many of the details are undocumented and I (and probably everyone else) have been relying on the CVS pre-commit checks (and now git commit/push hooks) to guide me.<BR>
<BR>
Where the git hooks deviate from the CVS checks (and they deviate in almost every possible way) I assumed that the commit rules were being updated. For example, I have already stopped using those BUG/ENH/PERF prefixes to many of my commit descriptions figuring that we were moving to a more standard git-style description.<BR>
<BR>
This email thread suggests that my assumption is wrong and that there has been no intentional change in these commit rules excepting where they cause undo stress upon the developer (but no one knows where that line is). May I humbly request that Kitware, gatekeeper of the holy repositories, provide edict to us sheep-like developers. I understand that this is unlikely to be the highest priority as we are still coming to terms with the new repositories and struggling to make an effective workflow. Nonetheless, I expect a lot of variability in style until then.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
On 4/23/10 1:05 PM, "Brad King" <<a href="brad.king@kitware.com">brad.king@kitware.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Brad King wrote:<BR>
> It looks like I accidentally left the message length enforcement on.<BR>
> However, other developers in this thread have expressed a liking for it.<BR>
> We should probably remove it on the server so developers don't have to<BR>
> rebase and edit long (possibly shared) histories just for that.<BR>
<BR>
For now I've disabled the message format check on VTK, ParaView, Xdmf,<BR>
and IceT. If developers reach a consensus to re-enable it I'll do so.<BR>
There are plenty of commits in the past that fail the check, so a few<BR>
more in the meantime won't hurt.<BR>
<BR>
-Brad<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE="1"><FONT FACE="Monaco, Courier New"><SPAN STYLE='font-size:7.5pt'><BR>
**** Kenneth Moreland<BR>
*** Sandia National Laboratories<BR>
*********** <BR>
*** *** *** email: <a href="kmorel@sandia.gov">kmorel@sandia.gov</a><BR>
** *** ** phone: (505) 844-8919<BR>
*** web: <a href="http://www.cs.unm.edu/~kmorel">http://www.cs.unm.edu/~kmorel</a><BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT>
</BODY>
</HTML>