From: Heiko Voigt <git-list@hvoigt.net>
To: Jakub Narebski <jnareb@gmail.com>
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 15:30:24 +0100 [thread overview]
Message-ID: <49A01000.2000308@hvoigt.net> (raw)
In-Reply-To: <m3k57jsx36.fsf@localhost.localdomain>
Jakub Narebski schrieb:
> Heiko Voigt <git-list@hvoigt.net> 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
next prev parent reply other threads:[~2009-02-21 14:37 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
2009-02-21 14:30 ` Heiko Voigt [this message]
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=49A01000.2000308@hvoigt.net \
--to=git-list@hvoigt.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--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).