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 07:05:56 +0530 [thread overview]
Message-ID: <20100204013556.GA2590@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.
I forgot... part of the reason this "copy all hooks over
each time you run install" is also to give people an easy
way to update the hooks when the repo was *copied* from
elsewhere, and not *created* by gitolite in the first place.
Basically I'm paranoid about that "update" hook, without
which the branch level access control doesn't work at all.
So this will still need to be done. Or you'll have to
provide some other command that will sweep through all repos
in the $REPO_BASE and check that the symlink is pointing to
the right place etc etc.
Any other ways of doing this? I'd rather keep it as is, if
it's OK with you, except for changing the cp to ln of course.
prev parent reply other threads:[~2010-02-04 1:36 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
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 [this message]
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=20100204013556.GA2590@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).