Re: cloning/pulling hooks
- From
Benjamin Collins <aggieben@gmail.com>
- Date
- Aug 29, 2007, 13:18 UTC
- Message-ID
- <b3889dff0708290618s79cffdb5nb6cc69d14efa8b9@mail.gmail.com>
- In-Reply-To
- <20070829095202.GE1219@pasky.or.cz>
On 8/29/07, Petr Baudis <pasky@suse.cz> wrote:
Show 5 quoted lines
> 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@gmail.com> http://bloggoergosum.us