Heiko Voigt <git-list@xxxxxxxxxx> writes: > How about combining my first approach with the second idea? Teach git > different default sets of hooks. So something like: > > git init --workflow="topic-branches" > > would initialize and install a certain set of hooks. > > 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. -- Jakub Narebski Poland ShadeHawk on #git -- 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
