From: PJ Weisberg <pj@irregularexpressions.net>
To: Hilco Wijbenga <hilco.wijbenga@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
Git Users <git@vger.kernel.org>
Subject: Re: Is there any way to make hooks part of the repository?
Date: Tue, 1 May 2012 14:59:18 -0700 [thread overview]
Message-ID: <CAJsNXT=niP2Ja-pSbvj-OGi5t0x0-Zxm3CdcY0nLs9ROdCG8hg@mail.gmail.com> (raw)
In-Reply-To: <CAE1pOi00Mr4dOj2ChTJU9XWypUAaVUDDa36-M7LA+9BixW0nKw@mail.gmail.com>
On Tue, May 1, 2012 at 2:09 PM, Hilco Wijbenga <hilco.wijbenga@gmail.com> wrote:
> On 1 May 2012 14:03, Junio C Hamano <gitster@pobox.com> wrote:
>
>> We've talked about something like that a few times in the past, but as far
>> as I (am concerned / remember) the conclusion has always been that is not
>> worth "standardizing", i.e. nothing a ./setup script in-tree or a Makefile
>> target cannot offer the same convenience.
>
> This would not keep things up-to-date, though, would it? It seems like
> yet another thing developers need to remember and do. I would prefer
> something more automatic.
Once your hooks are installed, couldn't your post-checkout and
post-merge hooks keep all the others up to date?
-PJ
Gehm's Corollary to Clark's Law: Any technology distinguishable from
magic is insufficiently advanced.
next prev parent reply other threads:[~2012-05-01 21:59 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 [this message]
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
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='CAJsNXT=niP2Ja-pSbvj-OGi5t0x0-Zxm3CdcY0nLs9ROdCG8hg@mail.gmail.com' \
--to=pj@irregularexpressions.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hilco.wijbenga@gmail.com \
--cc=merlyn@stonehenge.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).