From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Heiko Voigt <hvoigt@hvoigt.net>,
Git Mailing List <git@vger.kernel.org>,
Sitaram Chamarty <sitaramc@gmail.com>,
tv@eagain.net
Subject: Re: Re: [PATCH] Add USER environment variable to executed git commands when serving
Date: Wed, 3 Jun 2009 14:02:01 -0700 [thread overview]
Message-ID: <20090603210201.GP3355@spearce.org> (raw)
In-Reply-To: <robbat2-20090603T204719-922480112Z@orbis-terrarum.net>
"Robin H. Johnson" <robbat2@gentoo.org> wrote:
> On Wed, Jun 03, 2009 at 10:27:02PM +0200, Heiko Voigt wrote:
> > You are welcome. An interesting addition would be to propagate allowed
> > branchnames from gitosis.conf. That way you can implement write-
> > protected branches using an update hook.
> ...
> > A nice solution to steer this directly from gitosis.conf? I never got
> > around implementing it.
> Has anybody implemented something like cvs_acls.pl (used by FreeBSD) for
> Git?
contrib/hooks/update-paranoid ?
Perhaps the most flexible, and most paranoid, update hook available.
But it does require that the frontend set some sort of user identity.
I think it relies on UNIX uid, but its easy to hack to use an env
var instead from gitosis.
--
Shawn.
prev parent reply other threads:[~2009-06-03 21:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 4:02 gitosis question: identifying/logging remote user Sitaram Chamarty
2009-06-02 6:31 ` Robin H. Johnson
2009-06-02 13:19 ` Sitaram Chamarty
2009-06-02 20:21 ` Robin H. Johnson
2009-06-03 0:54 ` Sitaram Chamarty
2009-06-02 13:56 ` [PATCH] Add USER environment variable to executed git commands when serving Heiko Voigt
2009-06-03 1:04 ` Sitaram Chamarty
2009-06-03 6:24 ` Sitaram Chamarty
2009-06-03 20:27 ` Heiko Voigt
2009-06-03 20:50 ` Robin H. Johnson
2009-06-03 21:02 ` Shawn O. Pearce [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=20090603210201.GP3355@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=robbat2@gentoo.org \
--cc=sitaramc@gmail.com \
--cc=tv@eagain.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.