From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jonathan del Strother <jon.delStrother@bestbefore.tv>,
git@vger.kernel.org
Subject: Re: [PATCH/RFC] Add post-init hook
Date: Thu, 09 Oct 2008 04:24:29 -0700 [thread overview]
Message-ID: <7viqs2ovte.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081009014146.GA14204@coredump.intra.peff.net> (Jeff King's message of "Wed, 8 Oct 2008 21:41:46 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Oct 08, 2008 at 09:16:56AM +0100, Jonathan del Strother wrote:
> ...
>> I want symlinks so I only have to edit my hooks in one place whenever
>> I change them)
>
> This makes a lot of sense to me as a best-practice. I wonder if we
> wouldn't do better to add a core.symlink-templates option?
AFAIR, "git init" copies symlinks in templates as symlinks, so I do not
see why you would even want to have such an option.
Wouldn't it be better if users and installations with such a special
set of templates specified by core.template or --template prepare a
template directory with files and symbolic links of their liking? If
they want some hooks to point at the latest copy of installation specific
standard hook script, templates/hooks/$that_hook can be a symlink to the
real location, no?
next prev parent reply other threads:[~2008-10-09 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 23:10 [PATCH/RFC] Add post-init hook Jonathan del Strother
2008-10-08 1:53 ` Jeff King
2008-10-08 8:16 ` Jonathan del Strother
2008-10-09 1:41 ` Jeff King
2008-10-09 11:24 ` Junio C Hamano [this message]
2008-10-09 11:32 ` Jeff King
2008-10-09 11:34 ` Alex Riesen
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=7viqs2ovte.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jon.delStrother@bestbefore.tv \
--cc=peff@peff.net \
/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).