On 1 May 2012 14:03, Junio C Hamano <gitster@xxxxxxxxx> wrote: > merlyn@xxxxxxxxxxxxxx (Randal L. Schwartz) writes: > >>>>>>> "Junio" == Junio C Hamano <gitster@xxxxxxxxx> writes: >> >> Junio> By design. Do you want me to include "rm -fr ~hilco" in some hook of >> Junio> git.git repository? >> >> This just came up yesterday at $PRIMARY_CLIENT. One idea we kicked >> around was having a convention for storing the hooks-to-be-populated in >> ".githooks" in the repository tree, and then having clone notice that >> and offer to install them directly if from a trusted source, or at least >> move them into a disabled state in .git/hooks otherwise. > > We've talked about something like that a few times in the past, but as far > as I (am concerned / remember) the conclusion has always been that is not > worth "standardizing", i.e. nothing a ./setup script in-tree or a Makefile > target cannot offer the same convenience. This would not keep things up-to-date, though, would it? It seems like yet another thing developers need to remember and do. I would prefer something more automatic. -- 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