Jakub Narebski schrieb: > Heiko Voigt <git-list@xxxxxxxxxx> writes: >> Implement the possibility to propagate this setting to the server, by >> using a config variable or similar. This way only secure hooks will >> automatically be inherited and the user has the benefit of a more >> specific workflow support. > > Well, for an _installation_ of git you _have_ possibility to provide > hooks different than default ones, and that is via templates system. > With "git init" in already existing repository you would be able to > pick up new version of hooks. Should this decision really be on an installation basis? Would basing this decision on a project not be a better reflection of the reality? I have read some threads dealing with what a good book about git should contain. In these threads the keyword workflows was brought up quite often. So maybe it would also be good to support this topic a little more from the software side. cheers Heiko -- 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
