From: Thomas Rast <trast@student.ethz.ch>
To: Hilco Wijbenga <hilco.wijbenga@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Git Users <git@vger.kernel.org>
Subject: Re: Is there any way to make hooks part of the repository?
Date: Thu, 3 May 2012 11:00:10 +0200 [thread overview]
Message-ID: <87ipgdskpx.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <CAE1pOi1SLU5_eLr3ahiUjzQqPUnVPX70CPq=OW-o-85Lk43GwA@mail.gmail.com> (Hilco Wijbenga's message of "Wed, 2 May 2012 12:42:17 -0700")
Hilco Wijbenga <hilco.wijbenga@gmail.com> writes:
>> Matthieu is *not* talking about auditing nastiness going into the
>> project's repository; he is talking is about a chance to audit whatever
>> comes from the project's repository that *could* potentially contain some
>> nastiness before it causes harm to your working environment. In other
>> words, not *having* to trust what is in the project's repository, but
>> having a way to verify.
>
> Perhaps these automatic hooks should only be applicable for "outgoing"
> changes like commit and push? That way you can review the hooks before
> they run but you still have a chance to prevent developer errors from
> getting to the server/other people (which is really all I care about,
> I am looking for a way to protect developers from making silly
> mistakes).
Shouldn't those checks be made server-side with a pre-receive hook?
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-05-03 9:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 20:24 Is there any way to make hooks part of the repository? Hilco Wijbenga
2012-05-01 20:33 ` Junio C Hamano
2012-05-01 20:57 ` Randal L. Schwartz
2012-05-01 21:03 ` Junio C Hamano
2012-05-01 21:09 ` Hilco Wijbenga
2012-05-01 21:59 ` PJ Weisberg
2012-05-01 22:21 ` Hilco Wijbenga
2012-05-02 0:10 ` Nathan Gray
2012-05-02 0:18 ` Hilco Wijbenga
2012-05-01 21:07 ` Hilco Wijbenga
2012-05-01 21:00 ` Hilco Wijbenga
2012-05-02 6:38 ` Matthieu Moy
2012-05-02 19:10 ` Hilco Wijbenga
2012-05-02 19:27 ` Junio C Hamano
2012-05-02 19:42 ` Hilco Wijbenga
2012-05-03 9:00 ` Thomas Rast [this message]
2012-05-03 17:05 ` Hilco Wijbenga
2012-05-04 6:10 ` Johan Herland
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=87ipgdskpx.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hilco.wijbenga@gmail.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).