On 8/29/07, Petr Baudis <pasky@xxxxxxx> wrote: > But overally, I'm still not convinced that there is a feasible use-case > for the cloned hooks at all. Someone has a particular example? > > -- > Petr "Pasky" Baudis My group at work would like this capability. We have a homogeneous environment with well-known NFS shares, and some scripts that do things in this common environment (e.g., release scripts). It would be nice if when we do a clone, all the hook scripts (that would be valid on any machine, in any directory, for any user) would come with it. Of course, I understand why it's not already like that, particularly given the context of Linux development practices. Still - there are those of us that think this would be a great convenience. Having an option to git-clone to retrieve the parent's hook scripts would be preferable, and have git-clone just disable them by default. 'git-clone -t repo' or some such. -- Benjamin A. Collins <aggieben@xxxxxxxxx> http://bloggoergosum.us - 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
