From: Sitaram Chamarty <sitaram@atc.tcs.com>
To: martin f krafft <madduck@debian.org>
Cc: git discussion list <git@vger.kernel.org>,
Sitaram Chamarty <sitaramc@gmail.com>,
Teemu Matilainen <teemu.matilainen@iki.fi>
Subject: Re: [gitolite] symlink hooks instead of copying them
Date: Thu, 4 Feb 2010 06:58:40 +0530 [thread overview]
Message-ID: <20100204012840.GC497@atcmail.atc.tcs.com> (raw)
In-Reply-To: <20100203204723.GA30157@lapse.rw.madduck.net>
On Thu, Feb 04, 2010 at 09:47:23AM +1300, martin f krafft wrote:
> Dear Sitaram, dear Teemo, dear gitolite-fans,
>
> Gitolite currently copies hooks to repositories. For upgrades, it
> must thus ensure that all hooks are also upgraded.
>
> It occurs to me that this might be easier done using symlinks, or
> with a file that includes the master hook(s) in
> ~/.gitolite/src/hooks. Then, the hooks just have to be upgraded in
> one place.
>
> Do you see a reason not to do this via symlinks?
If you mean just the gitolite-specific hooks (the update
hook for all repos, and the post-update hook for the admin
repo) then no problem.
The other hooks I'd rather not assume anything about. The
current scheme forces an overwrite of the gitolite-specific
hooks, as well as any hooks given in src/hooks, each time an
"install" is done. It does not touch any *other* hooks,
which allows the admin to (via command line) place specific
hooks in specific repos manually if he wishes to.
I'm ok with symlinking stuff; a couple of "cp" commands
would change to "ln" :) Let me try it out (and make sure it
works for upgrades also...)
next prev parent reply other threads:[~2010-02-04 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 20:47 [gitolite] symlink hooks instead of copying them martin f krafft
2010-02-04 1:28 ` Sitaram Chamarty [this message]
2010-02-04 1:46 ` martin f krafft
2010-02-04 3:22 ` Sitaram Chamarty
2010-02-04 4:13 ` martin f krafft
2010-02-04 6:17 ` Bill Lear
2010-02-04 6:34 ` martin f krafft
2010-02-04 1:35 ` Sitaram Chamarty
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=20100204012840.GC497@atcmail.atc.tcs.com \
--to=sitaram@atc.tcs.com \
--cc=git@vger.kernel.org \
--cc=madduck@debian.org \
--cc=sitaramc@gmail.com \
--cc=teemu.matilainen@iki.fi \
/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).