Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: > Stephen Leake wrote: >> Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: >> >> > Ilya Bobyr wrote: >> >> On 4/21/2014 2:17 PM, Felipe Contreras wrote: >> >> > Ilya Bobyr wrote: >> >> > >> >> >> Also, most have names that start with either "pre-" or "post-". >> >> >> It seems reasonable for both "pre-update-branch" and >> >> >> "post-update-branch" to exist. >> >> > I don't see what would be the point in that. >> >> >> >> Do you see the point in the other hooks doing that? >> > >> > Yes, there a reason for the existance of those hooks. Now tell me why would >> > anybody use post-update-branch instead of pre-update-branch? >> >> I have a branch which should always be recompiled on update; >> post-update-branch would be a good place for that. > > And why would pre-update-branch not serve that purpose? Because the code that needs to be compiled is not yet in the workspace -- -- Stephe -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html