From: Jakub Narebski <jnareb@gmail.com>
To: Heiko Voigt <git-list@hvoigt.net>
Cc: Thomas Rast <trast@student.ethz.ch>,
Wincent Colaiuta <win@wincent.com>,
git@vger.kernel.org
Subject: Re: [RFC PATCH] hooks: add some defaults to support sane workflow to pre-commit
Date: Sat, 21 Feb 2009 06:05:25 -0800 (PST) [thread overview]
Message-ID: <m3k57jsx36.fsf@localhost.localdomain> (raw)
In-Reply-To: <49A00215.9070106@hvoigt.net>
Heiko Voigt <git-list@hvoigt.net> 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
next prev parent reply other threads:[~2009-02-21 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 18:13 [RFC PATCH] hooks: add some defaults to support sane workflow to pre-commit Heiko Voigt
2009-02-20 20:49 ` Wincent Colaiuta
2009-02-21 10:56 ` Heiko Voigt
2009-02-21 11:16 ` Thomas Rast
2009-02-21 13:31 ` Heiko Voigt
2009-02-21 14:05 ` Jakub Narebski [this message]
2009-02-21 14:30 ` Heiko Voigt
2009-02-23 18:41 ` Heiko Voigt
2009-10-19 8:50 ` Junio C Hamano
2009-10-20 19:59 ` Heiko Voigt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3k57jsx36.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git-list@hvoigt.net \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
--cc=win@wincent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).